-
-
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
mv: cannot remove '/volume1/@img_bkp_cache': Operation not permitted when moving Hyper Backup #54
Comments
Additional information in case it's needed:
|
Can you check if If this command returns nothing then it is empty:
Moving /volume1/@img_bkp_cache is the last step before starting Hyper Backup. So if /volume1/@img_bkp_cache is empty then you can start Hyper Backup from Package Center and it should all be okay. If /volume1/@img_bkp_cache is not empty, then try this:
|
The directory seems to be not empty:
It seems to have no actual files but only a folder structure:
Tried executing the |
DSM creates You can delete the empty
I'll change the script to delete |
Thank you. I tried the rm command above, and got:
|
btw, it a relinking expected after moving? |
Interesting. I just tried it on one of my Synology NAS and it worked. Try this:
|
Still not working |
Does the following command show that the
|
Yes. Seems
|
I would just leave the empty |
Leave the empty folder is okey. I'm not a fan of Windows but I wonder how does WinSCP make a difference? |
I often wonder how WinSCP can delete a folder that I can't delete via SSH. One thing we haven't tried, now that the folder is empty, is:
|
Guess I'll just leave it there. What protocol were you using when you can delete a folder that can't be deleted via SSH? |
Yes. I haven't found a way to avoid the relinking, but once it's done everything should work. |
SCP |
Did the script stop at that point or did it continue to the end? |
It stopped at that point. |
I got the following error when moving Hyper Backup:
Please tell me what should I do now. Thank you.
The text was updated successfully, but these errors were encountered: