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
Large S3 uploads fail #7410
Comments
I've updated to the snapshot build and did a test with a 15.7GB zip file. Took about an hour going to S3 East coast from LA. (I love how the east coast server is just as or sometimes faster than the west coast ones. Bigger tube I guess) I'm going to keep using the same file as a test for this ticket so everything remains same. (same file, internet connection, time of day... conditions) The upload completed successfully according to the Transfers window. I refreshed the bucket and the file size read 0. Closed restarted... same thing. Checked the bucket with another computer through a different IP... same thing. When downloading, it is just a 0 bite zip file. When I try to resume, I get transfer incomplete again and again with 419.4MB of 15.7GB. I would assume the pieces in the upload got lost and there's no map to say what goes where. I've successfully uploaded this file a few times (one zipped and one a QT MOV file) via CloudBerry. So I know it's possible. |
Oh and I've tried this twice. Same result. |
Version 4.4 (12588) - Same result. Screenshot attached. |
I have similar (if not the same) problems. The uploads complete successfully but result in 0KB files. This doesn't happen every time and sometimes happens with smaller (~15MB) files as well. I don't get any error messages and I've also had this problem before, I just rarely use S3. This week I have uploaded 28 ~2GB files and over a hundred 15MB files. Every 15MB file was uploaded succesfully and maybe 6 of the bigger files resulted in 0KB files. I have tried to upload and overwrite a 0Kb file but it doesn't help. If I delete the 0KB file first and then try to upload again it might work, usually doesn't. If I rename the file or delete and wait a while before uploading again I seem to get better odds that the file is actually written to S3. I'm running Versio 4.4 (12520) on OSX 10.8.4 |
Replying to [comment:8 probus]:
Thanks for your valuable report. We have made further fixes in 74ca4ff and 992b32f to make multipart uploads more reliable. Please try the latest build (0a48e4a or later). We will add more tests before closing this issue. |
I've been getting this error for years. I use Cloudberry running a VM but hate doing it. Thought I'd try again after a year of not using CD but it still fails.
2GB files... right now trying a 15GB one on a very fast internet connection. Getting 5-6MB per second up.
Same error I've been getting for years: I/O Error: upload failed. Skipped X bytes instead of X.
And you can't resume an upload. (as you should be able to with multipart uploads)
AAnnyyywwayyy. Screenshot attached.
Attachments
Screen Shot 2013-08-21 at 10.48.28 PM.png
(65.7 KiB)Screen Shot 2013-08-27 at 6.35.02 PM.png
(102.9 KiB)The text was updated successfully, but these errors were encountered: