On Aug 09 2015, Jeff Pence <[email protected]> wrote:
> [jeffrey@Ouarzazate ~]$ s3qladm --version
> S3QL 2.9
> [jeffrey@Ouarzazate ~]$ s3qladm upgrade s3://mumble
> Getting file system parameters..
> Ignoring locally cached metadata for upgrade.
> File system is damaged, need to run fsck before upgrade.
> Uncaught top-level exception:
> Traceback (most recent call last):
> File "/usr/bin/s3qladm", line 9, in <module>
> load_entry_point('s3ql==2.9', 'console_scripts', 's3qladm')()
> File "/usr/lib64/python3.4/site-packages/s3ql/adm.py", line 101, in main
> options.cachedir))
> File "/usr/lib64/python3.4/site-packages/s3ql/adm.py", line 287, in
> upgrade
> print(get_old_rev_msg(param['revision'], 'fsck.s3ql'))
> File "/usr/lib64/python3.4/site-packages/s3ql/adm.py", line 227, in
> get_old_rev_msg
> ''' % { 'version': REV_VER_MAP[rev],
> KeyError: 20
>
> Is it safe to run fsck.s3ql, or will that have unwanted side effects if the
> version isn't 2.9?
That simply won't work. You need to use fsck.s3ql from the S3QL version
that you last used to access the file system.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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.
