mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

work around minimum part size problem

Browse source 
When uploading the last part of a file, which was 640229 bytes, S3 rejected
that part: "Your proposed upload is smaller than the minimum allowed size"

I don't know what the minimum is, but the fix is just to include the last
part into the previous part. Since this can result in a part that's
double-sized, use half-sized parts normally.
This commit is contained in:
Joey Hess 2014-11-04 16:06:13 -04:00
parent ad2125e24a
commit a42022d8ff
2 changed files with 19 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/special_remotes/S3.mdwn
View file

@ -21,10 +21,14 @@ the S3 remote.
* `chunk` - Enables [[chunking]] when storing large files.
`chunk=1MiB` is a good starting point for chunking.
* `partsize` - Specifies the largest object to attempt to store in the
bucket. Multipart uploads will be used when storing larger objects.
This is not enabled by default, but can be enabled or changed at any
time. Setting `partsize=1GiB` is reasonable for S3.
* `partsize` - Amazon S3 only accepts uploads up to a certian file size,
and storing larger files requires a multipart upload process.
Setting `partsize=1GiB` is recommended for Amazon S3; this will
cause multipart uploads to be done using parts up to 1GiB in size.
This is not enabled by default, since other S3 implementations may
not support multipart uploads, but can be enabled or changed at any
time.
* `keyid` - Specifies the gpg key to use for [[encryption]].