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

Resume does not skip completed parts #9944

Closed
cyberduck opened this issue May 18, 2017 · 8 comments
Closed

Resume does not skip completed parts #9944

cyberduck opened this issue May 18, 2017 · 8 comments
Assignees
Labels
b2 Backblaze B2 Protocol Implementation bug fixed
Milestone

Comments

@cyberduck
Copy link
Collaborator

b95b27b created the issue

I filed an earlier bug about upload resume being broken for B2 in the 6.0.0 release. That was marked fixed in 6.0.1, thank you! I downloaded the 6.0.1 beta and retested. It is_better_ but still very problematic. I started an upload of a 376MB file using 2 upload connections. I stopped the upload just after 350MB. Since Cyberduck says it uses 100MB chunks, I expected it to resume at 300MB (or less ideally 200MB). Instead, upon resume, it started back at only 76MB complete. It looks like it chunked, sent the remainder chunk first(?), and then lost all the preceding chunks.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Referring to #9935.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I suspect you had multiple incomplete large file uploads pending for the same file. You can view unfinished large uploads in the browser by choosing View → Show Hidden Files.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Add test in 25d650f.

@cyberduck
Copy link
Collaborator Author

b95b27b commented

I am so sorry. Please be patient with me. I just retested and had exactly the same result. I was uploading a 376MB file using 2 upload connections. I stopped @ 350MB. I resumed and the resume started at 76MB. Mathematically there is no way using 100MB chunks that 350MB could have been transferred and only the single 76MB dwarf chunk was completed.

The documentation says chunking is activated when a file is greater than 200MB and it uses 100MB chunks. Is there a chance the documentation is wrong and you are using 200MB chunks? That could cause the observed result.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:5 TheBashar]:

The documentation says chunking is activated when a file is greater than 200MB and it uses 100MB chunks. Is there a chance the documentation is wrong and you are using 200MB chunks? That could cause the observed result.

I can confirm these are the current defaults.

@cyberduck
Copy link
Collaborator Author

b95b27b commented

Same test but with a 425MB file. Upload stopped at 410MB. Upload resumed at just 25MB.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Possible fix in c050499 to make sure we always take the last started upload.

@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
b2 Backblaze B2 Protocol Implementation bug fixed
Projects
None yet
Development

No branches or pull requests

2 participants