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

Multipart uploads not resumable #6208

Closed
cyberduck opened this issue Sep 7, 2011 · 13 comments
Closed

Multipart uploads not resumable #6208

cyberduck opened this issue Sep 7, 2011 · 13 comments
Assignees
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Sep 7, 2011

Aolchik created the issue

I'm trying to upload a large file to S3 (1GB).
The upload fails and resume is never enabled.
I have always to restart the upload.
The result is that I cannot upload the file.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 9, 2011

@dkocher commented

Currently when an upload to S3 fails we abort the multipart upload deleting all parts already transferred.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 9, 2011

@dkocher commented

What is the error message you get when the transfer is interrupted?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 1, 2011

ad82abc commented

I still have this problem. Do I have a setting that is incorrect? How can I enable this feature?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 1, 2011

@dkocher commented

Replying to [comment:4 jtcawrse]:

I still have this problem. Do I have a setting that is incorrect? How can I enable this feature?

Resumable multipart uploads are not currently enabled. We have to do more tests before we enable this feature. What is the error message you get for the interrupted transfers?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 1, 2011

ad82abc commented

Usually it is a broken pipe or some other network disconnect. My internet connection is not very stable.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 1, 2011

@dkocher commented

Replying to [comment:6 jtcawrse]:

Usually it is a broken pipe or some other network disconnect. My internet connection is not very stable.

We are tracking the same issue in #6391.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 3, 2011

ad82abc commented

Failure again. 4.5G upload. Build 4.2

This upload is essential to my work. Any help or advice appreciated.

Server: AmazonS3
PUT /061370%2Fpowerropeshddec11.mp4?uploadId=ScB3BtIHaRYxFnCz_lO_hGxApn6nx_XDr7OgjICj0d4kp6RP4z0USG520pHurG7iK5aQk7cETnh_2UerzWiKeA--&partNumber=20 HTTP/1.1
Date: Sat, 03 Dec 2011 07:38:16 GMT
Content-Type: application/octet-stream
Authorization: AWS=
Content-Length: 5242880
Host: mexifitdl.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.2 (Mac OS X/10.7.2) (i386)
Expect: 100-continue

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 3, 2011

ad82abc commented

tried again with build 4.2.1

x-amz-request-id: 7CEC650EC535DFC3
Date: Sat, 03 Dec 2011 15:12:50 GMT
Server: AmazonS3
PUT /061370%2Fpowerropeshddec11.mp4?uploadId=EzZy_0nYejCsUUYXrrjg3L3JbbjBiH84xzgLkK_EXXY.iRCktrV_q4BegYUaqkT4DKho5PMDWEBtG8X_9mXrFQ--&partNumber=8 HTTP/1.1
Date: Sat, 03 Dec 2011 15:12:39 GMT
Content-Type: application/octet-stream
Authorization: AWS c=
Content-Length: 5242880
Host: mexifitdl.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.2.1 (Mac OS X/10.7.2) (i386)
Expect: 100-continue

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 27, 2013

ac074e1 commented

This is still happening in Version 4.2.1 (9350).

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 4, 2013

7fdc851 commented

Same problem is, my file is 7.17go... Broken pipe (4.3.1).

Date: Sat, 04 May 2013 14:56:41 GMT
Server: AmazonS3
PUT /iPhoto_2006-2012.tar?uploadId=6GJ859iFc8yPuMYSaCMONAnRbV6sXCqt2bhx0kwz5zfSUq2kIPtzWJkmF0MeHCx.dThPSIqcD.KK2qHGkVKbxQ--&partNumber=10 HTTP/1.1
Date: Sat, 04 May 2013 14:56:38 GMT
Content-Type: application/octet-stream
Authorization: (hidden)
Content-Length: 5242880
Host: mes-backups.s3.amazonaws.com:80
Connection: Keep-Alive
User-Agent: Cyberduck/4.3.1 (Mac OS X/10.8.3) (i386)
Expect: 100-continue

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 5, 2013

7fdc851 commented

Due to cyberduck's bugs with multi-part upload (see my comment above), I uploaded my big file using s3tools (s3tools.org) from command line and it worked without any problem. My conclusion is Cyberduck seems to have some problem to upload multi-part files.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 29, 2013

@dkocher commented

#7273 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 31, 2013

@dkocher commented

In 1bdab5c.

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

No branches or pull requests

2 participants