Cyberduck Mountain Duck CLI

Opened 14 months ago

Last modified 14 months ago

#9944 reopened defect

Resume does not skip completed parts

Reported by: TheBashar Owned by: dkocher
Priority: normal Milestone: 6.0.1
Component: b2 Version: Nightly Build
Severity: major Keywords:
Cc: Architecture:
Platform:

Description

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 (4)

cd1.jpg (159.5 KB) - added by TheBashar 14 months ago.
Uploaded 350MB with 2 connections
cd2.jpg (151.8 KB) - added by TheBashar 14 months ago.
Stopped transfer after 350MB
cd3.jpg (131.8 KB) - added by TheBashar 14 months ago.
Can see partial upload, though no size shown
cd4.jpg (169.1 KB) - added by TheBashar 14 months ago.
Resume started back at 76MB

Download all attachments as: .zip

Change History (15)

comment:1 Changed 14 months ago by dkocher

Referring to #9935.

comment:2 Changed 14 months ago by dkocher

  • Milestone set to 6.0.1
  • Owner set to dkocher
  • Status changed from new to assigned

comment:3 Changed 14 months ago by dkocher

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.

comment:4 Changed 14 months ago by dkocher

  • Resolution set to worksforme
  • Status changed from assigned to closed

Add test in r40989.

Changed 14 months ago by TheBashar

Uploaded 350MB with 2 connections

Changed 14 months ago by TheBashar

Stopped transfer after 350MB

Changed 14 months ago by TheBashar

Can see partial upload, though no size shown

Changed 14 months ago by TheBashar

Resume started back at 76MB

comment:5 follow-up: Changed 14 months ago by TheBashar

  • Resolution worksforme deleted
  • Status changed from closed to reopened

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.

comment:6 in reply to: ↑ 5 Changed 14 months ago by dkocher

  • Status changed from reopened to new

Replying to 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.

comment:7 Changed 14 months ago by TheBashar

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

comment:8 Changed 14 months ago by dkocher

  • Summary changed from Resume Upload Mostly Broken for B2 on 6.0.1 to Resume does not skip completed parts

comment:9 Changed 14 months ago by dkocher

  • Milestone changed from 6.0.1 to 7.0

Ticket retargeted after milestone closed

comment:10 Changed 14 months ago by dkocher

  • Milestone changed from 7.0 to 6.0.1
  • Resolution set to fixed
  • Status changed from new to closed

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

comment:11 Changed 14 months ago by TheBashar

  • Resolution fixed deleted
  • Status changed from closed to reopened

Problem remains the same in build 6.1.0 24925, which I believe is after r41167.

Note: See TracTickets for help on using tickets.
swiss made software