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 files fails with failure to read attributes #8536

Closed
cyberduck opened this issue Feb 2, 2015 · 2 comments
Closed

Moving files fails with failure to read attributes #8536

cyberduck opened this issue Feb 2, 2015 · 2 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

3b6d8b3 created the issue

When I try to move more than say 40 or so files at once from an s3 bucket to a sub bucket, CyberDuck kicks "Failure to read attributes of " errors. Subsequent copies of files in bucket kick "Download . failed. The specified key does not exist. Please contact your web hosting service provider for assistance." errors. After which CyberDuck with refresh the directory listing and not show objects that have already been moved.

I can however copy smaller sets of files without errors (usually) but its tedious moving several thousand files by lots of 20 or 30.

I experienced this error with 4.6. Updated to 4.7 16654 by allowing update to use Snapshot Builds and still see the issue.

Log entries in Console show some Java stack traces with exceptions and some other error level output (attached


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Moving files in S3 is inefficient and error prone as it involves a copy operation followed by a delete.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed generic error in moving placeholders in 80fd13b.

@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 fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants