On Mar 01 2017, joseph via s3ql <[email protected]> wrote:
> I had an fsck of an s3ql filesystem on amazon s3 fail due to a full disk on
> the local machine. When I try to fsck the file system again, I get these
> errors:
>
> Backing up old metadata...
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
> retrying call to Backend.copy for the 3-th time...
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
> retrying call to Backend.copy for the 4-th time...
>
> Is this related to the recent s3 outage?
Most likely. S3QL isn't able to exchange data with the remote server.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
