I am in the process of crafting a s3ql backed backup solution. During the
development/testing I left the store mounted, installed some system updates
and rebooted.
Now I am unable to mount and/or check the store. Running 2.12 on
ArchLinux. It has been several hours since I last wrote to the store.
My last attempt was to delete the local metadata and have it rebuilt.
Same error as below.
Not sure what to do next or how to recover. Are these stores typically
this fragile?
Also, as a test I created a fresh mount, wrote to it, unmounted it, and
remounted it without any issues.
2015-02-04 16:56:35.635 9617:MainThread s3ql.deltadump.dump_metadata:
dump_table(ext_attributes): writing 0 rows
2015-02-04 16:56:35.635 9617:MainThread s3ql.fsck.main: Compressing and
uploading metadata...
2015-02-04 16:56:35.635 9617:MainThread s3ql.backends.s3c.open_write:
open_write(s3ql_metadata_new): start
2015-02-04 16:56:50.247 9617:MainThread s3ql.backends.s3c.close:
ObjectW(s3ql_metadata_new).close(): start
2015-02-04 16:56:50.247 9617:MainThread s3ql.backends.s3c._do_request:
preparing PUT /s3ql_metadata_new?None, qs=None
2015-02-04 16:56:50.247 9617:MainThread s3ql.backends.s3c._send_request:
_send_request(): PUT /s3ql_metadata_new
2015-02-04 16:56:50.248 9617:MainThread s3ql.backends.common.wrapped:
Encountered ConnectionClosed exception (connection closed unexpectedly),
retrying call to ObjectW.close for the 1-th time...
2015-02-04 16:56:50.268 9617:MainThread s3ql.backends.s3c.close:
ObjectW(s3ql_metadata_new).close(): start
2015-02-04 16:56:50.268 9617:MainThread s3ql.backends.s3c._do_request:
preparing PUT /s3ql_metadata_new?None, qs=None
2015-02-04 16:56:50.268 9617:MainThread s3ql.backends.s3c._send_request:
_send_request(): PUT /s3ql_metadata_new
2015-02-04 16:56:50.727 9617:MainThread root.excepthook: Uncaught top-level
exception:
Traceback (most recent call last):
File "/usr/bin/fsck.s3ql", line 9, in <module>
load_entry_point('s3ql==2.12', 'console_scripts', 'fsck.s3ql')()
File "/usr/lib/python3.4/site-packages/s3ql/fsck.py", line 1287, in main
is_compressed=True)
File "/usr/lib/python3.4/site-packages/s3ql/backends/common.py", line 46,
in wrapped
return method(*a, **kw)
File "/usr/lib/python3.4/site-packages/s3ql/backends/common.py", line
258, in perform_write
return fn(fh)
File "/usr/lib/python3.4/site-packages/s3ql/backends/comprenc.py", line
642, in __exit__
self.close()
File "/usr/lib/python3.4/site-packages/s3ql/backends/comprenc.py", line
636, in close
self.fh.close()
File "/usr/lib/python3.4/site-packages/s3ql/backends/common.py", line 46,
in wrapped
return method(*a, **kw)
File "/usr/lib/python3.4/site-packages/s3ql/backends/s3c.py", line 844,
in close
headers=self.headers, body=self.fh)
File "/usr/lib/python3.4/site-packages/s3ql/backends/s3c.py", line 407,
in _do_request
query_string=query_string, body=body)
File "/usr/lib/python3.4/site-packages/s3ql/backends/s3c.py", line 649,
in _send_request
copyfileobj(body, self.conn, BUFSIZE)
File "/usr/lib/python3.4/shutil.py", line 69, in copyfileobj
fdst.write(buf)
File "/usr/lib/python3.4/site-packages/dugong/__init__.py", line 653, in
write
eval_coroutine(self.co_write(buf), self.timeout)
File "/usr/lib/python3.4/site-packages/dugong/__init__.py", line 1396, in
eval_coroutine
if not next(crt).poll(timeout=timeout):
File "/usr/lib/python3.4/site-packages/dugong/__init__.py", line 679, in
co_write
yield from self._co_send(buf)
File "/usr/lib/python3.4/site-packages/dugong/__init__.py", line 619, in
_co_send
len_ = self._sock.send(buf)
File "/usr/lib/python3.4/ssl.py", line 679, in send
v = self._sslobj.write(data)
OSError: [Errno 14] Bad address
--
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.
