Leftover data after moving apps and files

[pfiorentino]

Hi there,

I’m working on migrating all my data and apps from Volume 1 (ext4) to Volume 5 (Btrfs) on my Synology NAS.
I want to remove Volume 1 completely, but I’ve run into some issues with leftover data that I can’t seem to fully move.

What I’ve done so far:
I used the 007revad Synology App Migration script to move all Synology applications from Volume 1 to Volume 5.

I used Synology Drive Admin Console to move Drive data (mainly Files Version datadbase) to Volume 5.

However, when I check Volume 1 with du -h, there are still ~11GB in @database and ~37GB @synologydrive folder remaining.

📸 I've attached screenshots of the du -h output for Volume 1 and the corresponding usage shown in DSM for Synology Drive.

Questions:
The @database folder still shows ~11GB even though I moved it using the script.
Is that expected?
Could there be a leftover DB cache or hidden files not moved?
The new @database folder on Volume 5 is something like 3.1GB only which is strange, isn't it?

The @synologydrive folder usage in Volume 1 matches what DSM shows, but I moved everything via the Drive Admin Console. Why hasn’t the data physically moved from Volume 1?
I see a @synologydrive folder on Volume 5 but it's only 1.1GB.

There are several other @ folders (e.g., @appstore, @apphome, etc.)
What are they? Are they safe to delete?

What's the cleanest and safest way to finalize this migration so I can remove Volume 1?

My goal is to completely remove Volume 1 to reclaim that storage and simplify the setup. I’d really appreciate any guidance on what’s safe to remove or if there are extra steps I missed.

Thanks in advance!

[007revad]

When the script "moves" @database it actually copies it to a new @database folder on the target volume (in case some app gets broken and I need to help the person recover). So if all your Synology apps are working as they should you can ignore /volume1/@database.

Are you sure there's no app left on volume 1? I'm curious why /volume1/@appstore is 111MB.

Moving the Synology Drive database in Synology Drive Admin moves @synologydrive so I have no idea why @synologydrive is still on volume1. Maybe a result of "moving" it from ext4 to btrfs.

What do the following return?

cat /var/packages/SynologyDrive/etc/sharesync/monitor.conf

cat /var/packages/SynologyDrive/etc/sharesync/service.conf

cat /var/packages/SynologyDrive/etc/db-path.conf

sudo readlink /var/packages/SynologyDrive/etc/repo

[pfiorentino]

For the record, I just submitted a new PR adding those findings to the README.md file and bash script Synology Drive message: #202

[007revad]

Very nice PR

[pfiorentino]

Hehe thanks :)

I plan to create a new one soon to add that the File Versioning data is lost if the Volume is removed.

[007revad]

I thought you might :o)

[pfiorentino]

Here we go :) → #210