Cyberduck Mountain Duck CLI

#9131 closed defect (fixed)

Files greater than 100GB fail to upload

Reported by: jmamma Owned by: dkocher
Priority: high Milestone: 4.8
Component: openstack Version: 4.7.3
Severity: critical Keywords:
Cc: Architecture:

Description (last modified by dkocher)

Cyberduck has an arbitrary 100GB Object Size limit.

Observed Behavior:

When uploading an object larger than 100GB to Swift Storage, all segments will be transferred but the complete operation will fail at 100%.

Request Entity Too Large. 413 Request Entity Too Large

The Object manifest is not created.

It appears to be related to the design decision below:

We changed the part size for multipart uploads to 10MB in r14143 to allow multipart uploads up to 100GB in total size due to the maximum number of parts restriction of 10'000 by S3. Please try with the latest ​snapshot build available and reopen this ticket if you are still having this issue.


From my understanding you're failing at objects greater than 100GB to prevent more than 10,000 segment being created (an S3 limit). OpenStack Swift does not have a hard upper limit on the total number of objects stored in a container.


I've been able to override the default user setting: openstack.upload.largeobject.size to 1,048,576,000 (1GB) which is approximately the default segment size used by the Python Swift Client and increasing the Cyberduck object size limit to 1TB.

Manually editing the Cyberduck user.config xml file is a less than desirable solution for our users, who routinely upload 100GB or larger files.

Change History (6)

comment:1 Changed on Nov 24, 2015 at 5:11:53 AM by jmamma

  • Summary changed from Arbitrary Swift Object Size Limit 100GB to Files greater than 100GB fail to upload to Swift.

comment:2 Changed on Nov 24, 2015 at 11:06:29 AM by dkocher

  • Milestone set to 4.8
  • Status changed from new to assigned

comment:3 Changed on Nov 25, 2015 at 2:26:22 PM by dkocher

  • Description modified (diff)
  • Summary changed from Files greater than 100GB fail to upload to Swift. to Files greater than 100GB fail to upload

Thanks for your detailed bug report.

comment:4 Changed on Nov 25, 2015 at 2:27:09 PM by dkocher

See also #9134.

comment:5 Changed on Nov 25, 2015 at 2:32:30 PM by dkocher

The 413 error response is possibly due to the large manifest files given the thousands of segment names.

comment:6 Changed on Nov 25, 2015 at 2:34:36 PM by dkocher

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

Revert in r18555.

Note: See TracTickets for help on using tickets.