On Wednesday, March 1, 2017 at 3:33:08 PM UTC-8, Nikolaus Rath wrote: > > On Mar 01 2017, joseph via s3ql <[email protected] <javascript:>> > 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. > > I ran s3ql.fsck again with the --debug flag, and it's getting stuck with the following:
2017-03-02 18:03:12.438 10677:MainThread (name)s.copy: copy(s3ql_metadata_bak_6, s3ql_metadata_bak_7): start 2017-03-02 18:03:12.438 10677:MainThread (name)s._do_request: preparing PUT /s3ql_metadata_bak_7?None, qs=None 2017-03-02 18:03:12.438 10677:MainThread (name)s._send_request: _send_request(): PUT /s3ql_metadata_bak_7 2017-03-02 18:03:22.985 10677:MainThread (name)s.wrapped: Encountered ConnectionTimedOut exception (send/recv timeout exceeded), retrying call to Backend.copy for the 7-th time... Is there anything I can do about this, or should I just delete this s3ql instance and start again? Joseph -- 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.
