Skip to content
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

Mountain Duck Unexpected Behavior Compromises Integrity of Files in Cloud Storage #11895

Closed
cyberduck opened this issue Nov 3, 2021 · 1 comment
Labels
bug googledrive Google Drive Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

a3a72a4 created the issue

Used Mountain Duck v4.7.2, which I recently licensed, to mount Google Drive (with Cryptomator) while traveling to read and write files directly without sync to local drive, which is left at home. It is configured this way because I use Google Drive primarily (although not exclusively) as a backup of my external hard disk at home. Disruption of internet connect would cause open files on Google Drive to be corrupted and become unreadable. Disruptions have also caused an entire folder to disappear without a trace. I have had to restore these files when I got home by sync'ing the same from my external disk back to Google Drive.

First, I wouldn't expect open files to get corrupted only because an internet connection is interrupted but this happens each and every time. Second, I wouldn't expect folders to disappear for no reason.

If these are expected behaviors, I'd be better off using Cyberduck, which is free, only to download files for offline use rather than using the paid Mountain Duck program, which is suppose to allow me to mount and use cloud storage much like a local drive.

Please let me know what I should expect in terms of resolution. Thank you!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Could you please upgrade to version 4.8.0 and send us the log output when you can reproduce the issue to [mailto:support@mountainduck.io] where we are happy to have a close look at the issue.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug googledrive Google Drive Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant