You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've been trying to use Cyberduck and Mountainduck to make backups of my files on a Linux server.
As I start uploading to a vault on the server, at some point I will randomly start to get write errors, which will end up having folders which are not accessible anymore, so I can't open them nor delete them. Also trying to calculate the folder size form the infos will end up with the "no such file or directory".
What I've been able to verify, is that those related encripted directories are actually missing and, if I try to create them manually in the "d" directory (when it's encrypted, of course), the unaccessible folder will then become usable or at least deletable.
The problem is that those orphan directories are so many that it makes the job impossible, so the only option left is delete the entire vault.
This problem occurred Both with Cyberduck and Mountainduck.
Hi,
I've been trying to use Cyberduck and Mountainduck to make backups of my files on a Linux server.
As I start uploading to a vault on the server, at some point I will randomly start to get write errors, which will end up having folders which are not accessible anymore, so I can't open them nor delete them. Also trying to calculate the folder size form the infos will end up with the "no such file or directory".
What I've been able to verify, is that those related encripted directories are actually missing and, if I try to create them manually in the "d" directory (when it's encrypted, of course), the unaccessible folder will then become usable or at least deletable.
The problem is that those orphan directories are so many that it makes the job impossible, so the only option left is delete the entire vault.
This problem occurred Both with Cyberduck and Mountainduck.
Regards
Attachments
2021-01-07_110310.jpg
(356.7 KiB)The text was updated successfully, but these errors were encountered: