-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synology Drive folder size issue after moving #55
Comments
Looking in The script does not edit this symlink! I'm not sure why nobody has noticed this issue before. Does this return volume1 or volume2?
If the symlink still points to volume1:
|
I've fixed it in https://github.com/007revad/Synology_app_mover/releases/tag/v3.0.49 But you'll still need to do the following to fix your Synology Drive:
|
Now the weird thing comes:
I've done nothing but it's already pointed to volume2. I still see 913.4GB of File Versions on Admin Console. Guess I shouldn't change Package Usage to volume 2 before moving using this script? |
Update: I ended up uninstalling Synology Drive, and those spaces are finally freed up. |
After re-installing Synology Drive was all your settings and data still showing in drive and on volume 2? |
I chose to remove all data when uninstalling, so it's a fresh install. I see 1GB of File Version in volume 2 now. |
I was moving Synology Drive from volume1 to volume2. Earlier I went to Drive Admin Console and set Settings-Package Usage-Location to volume2. Then I moved Synology Drive using this script.
Before moving, the "usage" on the Admin Console reports the File Versions take about 900GB. After moving, it becomes 1.4TB. Not sure why this is happening. I see
/volume1/@synologydrive
was still taking up space:And
/volume2/@synologydrive
is taking up space too:I want to remove these File Versions to free up space, so I go to Admin Console and disable file versioning of all folders. It should free up space in the background. So I waited for an hour. But it turns out only
@synologydrive
on volume 1 is cleaned. Volume 2 seems to be intact:And Admin Console still shows 913.4GB of File Versions after refreshing. It should be ~0GB. Something weird must be happening...
The text was updated successfully, but these errors were encountered: