Hi.
I attempted the following:
* Built with the patch applied on a jessie chroot
* installed s3ql
* On a wheezy system mkfs.s3ql, mount and add some data. unmount.
* On my patched jessie system run s3qladm upgrade
So far so good.
Then run fsck.s3ql.
It looks like it has trouble with the old metadata:
Backing up old metadata...
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 710, in _extractmeta
return safe_unpickle(b64decode(buf), encoding='latin1')
File "/usr/lib/s3ql/s3ql/backends/common.py", line 629, in
safe_unpickle
encoding=encoding, errors=errors)
File "/usr/lib/s3ql/s3ql/backends/common.py", line 613, in
safe_unpickle_fh
raise pickle.UnpicklingError('opcode %s is unsafe' %
opcode.name)
_pickle.UnpicklingError: opcode NEWOBJ is unsafe
During handling of the above exception, another
exception occurred:
Traceback (most recent call last):
File "/usr/bin/fsck.s3ql", line 9, in <module>
load_entry_point('s3ql==2.11.1',
'console_scripts', 'fsck.s3ql')()
File "/usr/lib/s3ql/s3ql/fsck.py", line 1224, in
main
cycle_metadata(backend)
File "/usr/lib/s3ql/s3ql/metadata.py", line
121, in cycle_metadata
cycle_fn("s3ql_metadata_bak_%d" % i,
"s3ql_metadata_bak_%d" % (i + 1))
File "/usr/lib/s3ql/s3ql/backends/comprenc.py",
line 290, in copy
self._copy_or_rename(src, dest, rename=False,
metadata=metadata)
File "/usr/lib/s3ql/s3ql/backends/comprenc.py",
line 299, in _copy_or_rename
meta_raw = self.backend.lookup(src)
File "/usr/lib/s3ql/s3ql/backends/common.py",
line 46, in wrapped
It may be as simple as ignoring unsafe pickles in old metadata.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
