On Aug 10 2018, drobertsonad...@gmail.com wrote:
> But a few days ago the mount went offline with the error:
> *s3ql.backends.s3c.HTTPError:
> 413 Request Entity Too Large*
[...]
> s3ql.metadata.upload_metadata: Compressing and uploading metadata...
> 2018-08-08 15:41:03.977 18159:Metadata-Upload
On Saturday, August 11, 2018 at 7:34:29 PM UTC+10, Nikolaus Rath wrote:
>
> On Aug 10 2018, drobert...@gmail.com wrote:
> > But a few days ago the mount went offline with the error:
> *s3ql.backends.s3c.HTTPError:
> > 413 Request Entity Too Large*
> [...]
> > s3ql.metadata.upload_metadata:
On Saturday, August 11, 2018 at 9:34:54 PM UTC+10, drobert...@gmail.com
wrote:
>
>
>
> On Saturday, August 11, 2018 at 7:34:29 PM UTC+10, Nikolaus Rath wrote:
>>
>> On Aug 10 2018, drobert...@gmail.com wrote:
>> > But a few days ago the mount went offline with the error:
>> *s3ql.backends.s3c.
.. or thinking this from the other side.. the last successful upload of
metadata is under the limit, so if I do an fsck / mount or clone using only
the remote data I should get it accessible so that I can take required
evasive action (move to S3 or nfs? break down into X smaller mounts?)
--
Yo
On Aug 11 2018, drobertsonad...@gmail.com wrote:
> On Saturday, August 11, 2018 at 7:34:29 PM UTC+10, Nikolaus Rath wrote:
>>
>> On Aug 10 2018, drobert...@gmail.com wrote:
>> > But a few days ago the mount went offline with the error:
>> *s3ql.backends.s3c.HTTPError:
>> > 413 Request Entity To
