Hi all,
I'm running into the same issue here with a slight twist.
Server crashed. Seems 2.13 was installed via apt-get update. We had to
upgrade the s3ql filesystem, but the timeout issue with server was making
this infeasible (13% in 15hours).
So we tried to see if we could cancel the upgrade and mount that s3ql files
(simply to copy newest files to a new hard drive we set up because of this)
using the older 2.12 that we rebuilt locally.
This caused the system to be "confused if it was 2.12 or 2.13 and nothing
worked.
I followed direction in this thread but now I'm stuck at this error.
Traceback (most recent call last):
File "./bin/fsck.s3ql", line 26, in <module>
s3ql.fsck.main(sys.argv[1:])
File "/user/s3ql-2.12/src/s3ql/fsck.py", line 1241, in main
backend.perform_read(do_read, "s3ql_metadata")
File "/user/s3ql-2.12/src/s3ql/backends/common.py", line 46, in wrapped
return method(*a, **kw)
File "/user/s3ql-2.12/src/s3ql/backends/common.py", line 235, in
perform_read
fh = self.open_read(key)
File "/user/s3ql-2.12/src/s3ql/backends/comprenc.py", line 158, in
open_read
meta_raw = self._convert_legacy_metadata(fh.metadata)
File "/user/s3ql-2.12/src/s3ql/backends/comprenc.py", line 383, in
_convert_legacy_metadata
raise CorruptedObjectError('meta key data is missing')
s3ql.backends.common.CorruptedObjectError: meta key data is missing
How do I get it to use one of the backups for the metadata?
On Tuesday, January 6, 2015 at 2:09:55 PM UTC-5, Eric Eijkelenboom wrote:
>
> Hi Nikolaus
>
> After replacing one more occurrence of 's3ql_metadata' with
> 's3ql_metadata_bak_0' (in fsck.py, line 1242), I managed to run fsck
> successfully!
>
> Thanks a million :)
>
> BR, Eric
>
--
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.
