-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Comments
Currently when an upload to S3 fails we abort the multipart upload deleting all parts already transferred. |
What is the error message you get when the transfer is interrupted? |
I still have this problem. Do I have a setting that is incorrect? How can I enable this feature? |
Replying to [comment:4 jtcawrse]:
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? |
Usually it is a broken pipe or some other network disconnect. My internet connection is not very stable. |
Failure again. 4.5G upload. Build 4.2 This upload is essential to my work. Any help or advice appreciated.
|
tried again with build 4.2.1
|
This is still happening in Version 4.2.1 (9350). |
Same problem is, my file is 7.17go... Broken pipe (4.3.1).
|
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. |
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.
The text was updated successfully, but these errors were encountered: