[Cyberduck-trac] [Cyberduck] #10612: Failure proposed upload exceeds the maximum allowed size

Cyberduck trac at cyberduck.io
Fri Feb 22 14:49:38 UTC 2019

#10612: Failure proposed upload exceeds the maximum allowed size
 Reporter:  MarkBlaise   |         Owner:  dkocher
     Type:  defect       |        Status:  assigned
 Priority:  normal       |     Milestone:  6.9.4
Component:  s3           |       Version:  6.9.0
 Severity:  normal       |    Resolution:
 Keywords:               |  Architecture:  Intel
 Platform:  Windows 8.1  |

Comment (by MarkBlaise):

 Yesterday (21-Feb), dkocher said that I should increase the "part size"
 from 10 MB to 104857600 (100 MiB). With 10,000 parts, the max object size
 would then be about 976 GiB - plenty for my anticipated use.

 This morning there was additional information about an "off by 1" error
 regarding the maximum number of parts, and the fallback of PUT-ting the
 entire object fails.

 So should I still try increasing the part size? Or will there be a fixed
 Cyberduck build soon?

 If I should change the part size .... I'm not sure what to do with

 '''defaults write ch.sudo.cyberduck s3.upload.multipart.size 104857600'''

 Sorry for bring obtuse, but please explain.

Ticket URL: <https://trac.cyberduck.io/ticket/10612#comment:19>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list