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

Moving to another bucket causes data loss if copy fails #7638

Closed
cyberduck opened this issue Nov 24, 2013 · 2 comments
Closed

Moving to another bucket causes data loss if copy fails #7638

cyberduck opened this issue Nov 24, 2013 · 2 comments
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

9f168e9 created the issue

We have verified that dragging a file from one S3 bucket to another using Cyberduck causes the file to be completely lost if the upload fails. That is because the client sends a /DELETE command to the original bucket to delete the file even when the upload operation failed.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer (⌘-L). That should not be the case as the delete operation is only sent whenno I/O error occurs or the server does not reply with an error response.

@cyberduck
Copy link
Collaborator Author

9f168e9 commented

As with all exact sciences, we can no longer replicate this issue using a set of test files. ;)

This incident, however, highlighted the need to turn on versioning on our S3 buckets. Lesson learned.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants