Hello.
About a year ago I started an upgrade on an online filesystem.
I unfortunately don't know which version. I am nearly 100% sure that the
upgrade was either to 2.28 or even an earlier version.
During the update files were missing and I decided to copy everything to a
local disk before continuing the upgrade process. This took until now.
Unfortunately I can neither continue to upgrade, fsck or mount the
filesystem.
Version 2.28 says (`s3qladm --debug upgrade
local:///run/media/cl/disk1/cl/christian/`)
2019-06-26 14:04:25.058 11301 INFO MainThread s3ql.adm.upgrade: Getting
file system parameters..
2019-06-26 14:04:25.059 11301 ERROR MainThread root.excepthook: Backend
data corrupted, or file system revision needs upgrade.
Version 2.27.1 says (same command):
2019-06-26 14:03:31.840 10810 INFO MainThread s3ql.adm.upgrade: Getting
file system parameters..
2019-06-26 14:03:31.900 10810 ERROR MainThread root.excepthook: Uncaught
top-level exception:
Traceback (most recent call last):
File "/usr/bin/s3qladm", line 11, in <module>
load_entry_point('s3ql==2.27.1', 'console_scripts', 's3qladm')()
File "/usr/lib/python3.7/site-packages/s3ql/adm.py", line 94, in main
return upgrade(options)
File "/usr/lib/python3.7/site-packages/s3ql/common.py", line 433, in
wrapper
return fn(*a, **kw)
File "/usr/lib/python3.7/site-packages/s3ql/adm.py", line 240, in upgrade
param = backend.lookup('s3ql_metadata')
File "/usr/lib/python3.7/site-packages/s3ql/backends/comprenc.py", line
72, in lookup
meta_raw = self.backend.lookup(key)
File "/usr/lib/python3.7/site-packages/s3ql/backends/local.py", line 60,
in lookup
return _read_meta(src)
File "/usr/lib/python3.7/site-packages/s3ql/backends/local.py", line 241,
in _read_meta
raise CorruptedObjectError('Invalid object header: %r' % buf)
s3ql.backends.common.CorruptedObjectError: Invalid object header:
b'BZh91AY&S'
The 'BZh91AY&S' seems to come from one of the metadata files. A head -n 1
displays these characters for
s3ql_metadata_bak_0
s3ql_metadata_bak_1
s3ql_metadata_bak_2
s3ql_metadata_bak_3 and
s3ql_metadata_bak_4
s3qladm download-metadata skips all metadata files:
ERROR: Error retrieving information about s3ql_metadata, skipping
(same for all other bak files)
All metadata files are bzip2 files:
file s3ql_metadata*
s3ql_metadata: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_0: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_1: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_10: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_2: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_3: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_4: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_5: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_6: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_7: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_8: bzip2 compressed data, block size = 900k
s3ql_metadata_bak_9: bzip2 compressed data, block size = 900k
s3ql_metadata_new: bzip2 compressed data, block size = 900k
This is the content of my authinfo2:
=====
[s3ql]
storage-url: local:///run/media/cl/disk1/
fs-passphrase: B5mJhEEQu2MhGR8yBh55L
=====
I still have the db and param file from the online filesystem.
xx.param:
{ 'revision': 23, 'seq_no': 18, 'label': '', 'max_obj_size': 10485760,
'needs_fsck': False, 'inode_gen': 0, 'max_inode': 108788, 'last_fsck':
1511608008.239305, 'last-modified': 1511612643.0979273 }
last-modified: Saturday, November 25, 2017
Do you have any idea, what I am doing wrong?
regards
Christian
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/CAFF6WSEKD-GHbvXhCOYnRVampWo%3DiPLBSTjAr-exYLRAUFqzaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
