Firstly thanks for the fix of Issue 137 on bitbucket.
Took me a while to getting round to trying it out.
Well now I have a new one for you
With the fix 2.9-2 works perfectly but even with a clean umount and then an
upgrade to 2.13-1 (I'm running fedora 21 btw) every time i try to mount or
fsck the filesystem I get the following traceback.
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/bin/mount.s3ql", line 9, in <module>
load_entry_point('s3ql==2.13', 'console_scripts', 'mount.s3ql')()
File "/usr/lib64/python3.4/site-packages/s3ql/mount.py", line 128, in main
(param, db) = get_metadata(backend, cachepath)
File "/usr/lib64/python3.4/site-packages/s3ql/mount.py", line 391, in
get_metadata
param = backend.lookup('s3ql_metadata')
File "/usr/lib64/python3.4/site-packages/s3ql/backends/comprenc.py", line
76, in lookup
return self._verify_meta(key, meta_raw)[1]
File "/usr/lib64/python3.4/site-packages/s3ql/backends/comprenc.py", line
140, in _verify_meta
% (stored_key, key))
s3ql.backends.common.CorruptedObjectError: Object content does not match
its key (s3ql_metadata_new vs s3ql_metadata)
If I revert back to 2.9-2 it works fine.
On a side note is there anyway to donate to the project?
Thanks again
Raz
<https://bitbucket.org/nikratio/s3ql/issues?status=resolved>
--
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.
