Synology Drive leaves large (orphaned?) data after moving

[sipaan]

Hi,

First of all, thanks for this great script!

I have a question about Synology Drive after moving it to a new volume.

My situation
I moved Synology Drive from volume2 to volume3. Both volumes are BTRFS. After the move, I noticed that @synologydrive folder on volume2 still contains 2.7 TB of data, while the new location on volume3 only shows about 19 GB.
Synology Drive is working fine and pointing to volume3.

My questions

Is this expected behavior? I saw the note in the README about BTRFS snapshots handling versioning differently, but I'm not sure if the old @synologydrive folder is still needed or if it's orphaned.

Is there a safe way to verify that the old data is truly orphaned before deleting it?

What I found

Drive config files point to volume3
Active SQLite databases are on volume3 (with .sqlite-wal files)
Drive Admin Console shows 2.8 TB "File Versions" which is confusing

Thanks!

[007revad]

The Synology Drive database probably contains references to the old versions on /volume2/@synologydrive

I would wait a week or two to see if the /volume2/@synologydrive starts to increase in size. The /volume3/@synologydrive should stay the same size or get smaller as older versions automatically get deleted.

Or you could just delete File Versions in Drive Admin Console that are older than the day you moved Synology Drive to volume3.

[abol01]

I've also got about 410GB of data thats still sitting on the old volume since the middle of December. I thought based on your comment here, that it would eventually clean itself up but I dont think its shrinking. I want to remove the old volume at some point as I was planning on re-purposing the disks. Is there any way to confirm that the data wont be lost by removing it? I didnt see any easy way to go into the Synology Drive Admin center and remove all the old versions.

My old volume (volume2) is a BTRFS volume that I moved to my new BTRFS volume (volume1).