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

Jump to bottom

Proposed upload exceeds the maximum allowed size #7772

Closed
cyberduck opened this issue Feb 3, 2014 · 2 comments
Closed

Proposed upload exceeds the maximum allowed size #7772

cyberduck opened this issue Feb 3, 2014 · 2 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
4.4.4

Comments

@cyberduck
Copy link
Collaborator

05f871f created the issue

Hello, I've been trying to upload a 75GB file to Amazon S3 without success.

I've tried twice with the current version. All upload parts appear to succeed, and I am able to stop and resume the connection, and also resume after a network connection failure, but on the last part, it reports this error. It never "completes" the upload, and the file is never visible in the bucket.

My transfer log is attached. It has all of the second upload attempt, and I think at least the end of the first upload attempt.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

We changed the part size for multipart uploads to 10MB in 7b77f76 to allow multipart uploads up to 100GB in total size due to the maximum number of parts restriction of 10'000 by S3. Please try with the latest snapshot build available and reopen this ticket if you are still having this issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The first failing request with part number 10001 that exceeds the maximum allowed part numbers.

PUT /vitorio-macbookair-jan2014.dmg?uploadId=YKsMV3EBieZyS8YjFqyPMlJE7jkYQrziWbIDE6ZjEIy3Er7F7zzz251PfEfloPXjSne5PNEpzN1SeVziwdCT7A--&partNumber=10001 HTTP/1.1
Date: Sun, 02 Feb 2014 23:11:44 GMT
Content-Type: application/octet-stream
Authorization: AWS AKIAJP37KLPYNJNFL42Q:suo+wbyuQ+D5yWCFzYrlkM7MHQI=
Content-Length: 2031
Host: vitorio.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.4.3 (Mac OS X/10.8.5) (x86_64)
Expect: 100-continue
HTTP/1.1 400 Bad Request
x-amz-request-id: F62AD349F7EBE3F7
x-amz-id-2: Pnpi5g53N4wNOzTreCUKSTO4wutmZKSAntTBiWhvpqTL5OFXJ6SbIIWEDu4mKkiM
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Sun, 02 Feb 2014 23:11:43 GMT
Connection: close
Server: AmazonS3

@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.
Assignees

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.4.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck