[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Connection reset by peer
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Connection reset by peer |
Date: |
Wed, 27 Jun 2018 11:08:40 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 |
no problem Oli. obviously i wanted write 5GB below though.
to clarify for the ml archives. just reread the link below and it says
"
Upload objects in a single operation—With a *single PUT operation*, you can
upload objects up to *5 GB* in size.
"
and
"
You can use a *multipart upload* for objects from *5 MB to 5 TB* in size.
"
so for files >5GB you will need to enable --s3-use-multiprocessing as you did..
regards ede/duply.net
PS: it would be interesting to know what happens if the signature is <5MB as it
says above that there is this minimum size.
On 26.06.2018 23:00, Oliver Cole wrote:
> So, obviously 7.1GB < 5TB - I assume you're talking about the single
> operation 5GB upload limit?
>
> So for the archives, I seem to have solved this problem with
> --s3-use-multiprocessing:
>
> "If enabled, files duplicity uploads to S3 will be split into chunks and
> uploaded in parallel. Useful if you want to saturate your bandwidth or if
> large files are failing during upload."
>
> Thanks Edgar!
>
> On 10/06/2018 14:25, address@hidden wrote:
>> On 6/8/2018 17:54, Oliver Cole wrote:
>>> I also don't understand why it's failing during this signature upload, and
>>> none of the previous ones? Is it just too big?
>>>
>>> $ du -h duplicity-full-signatures.[...].sigtar.gpg
>>> 7.1G duplicity-full-signatures.[...].sigtar.gpg
>>>
>>> Oli
>>
>> it says 5TB here
>> https://docs.aws.amazon.com/AmazonS3/latest/dev/UploadingObjects.html
>>
>> so yeah, probably.. ede/duply.net
>>