Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Thanks for your report.

This issue has been added to the tracker:
https://winscp.net/tracker/1764

If you send me an email, I will send you back a development version of WinSCP for testing. Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.
KernelPanic

The issue is the multipart chunk size...
This is defined in the libs3. (s3.c)
#define MULTIPART_CHUNK_SIZE (15 << 20) // multipart is 15M
Making this 30M would allow for 100GB transfers, 60M for 200GB transfers.

The upstream project (libs3) has updated this to:
#define MULTIPART_CHUNK_SIZE (768 << 20) // multipart is 768M

Can winscp please be rebased with the updated libs3?
KernelPanic

sorry, this occurs at 50Gb, not 100Gb.
KernelPanic

Large (GT100GB) uploads to S3 fail

Error: Part number must be an integer between 1 and 10000, inclusive Extra Details: ArgumentName: part Number, Argument Value: 10001,

Winscp should use a larger value for the multipart, or allow a configuration option to set this.