I managed to upgrade the 1.16 fs to 2.9 using a clean cachedir.
Now 2.16 (from repo) chokes while mounting the bucket:
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/bin/fsck.s3ql", line 9, in <module>
load_entry_point('s3ql==2.14', 'console_scripts', 'fsck.s3ql')()
File "/usr/lib/s3ql/s3ql/fsck.py", line 1162, in main
seq_no = get_seq_no(backend)
File "/usr/lib/s3ql/s3ql/common.py", line 54, in get_seq_no
while ('s3ql_seq_no_%d' % seq_no) not in backend:
File "/usr/lib/s3ql/s3ql/backends/common.py", line 271, in __contains__
return self.contains(key)
File "/usr/lib/s3ql/s3ql/backends/comprenc.py", line 287, in contains
return self.backend.contains(key)
File "/usr/lib/s3ql/s3ql/backends/common.py", line 438, in contains
self.lookup(key)
File "/usr/lib/s3ql/s3ql/backends/common.py", line 107, in wrapped
return method(*a, **kw)
File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 279, in lookup
return self._extractmeta(resp, key)
File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 742, in _extractmeta
raise CorruptedObjectError('Invalid metadata format: %s' % format_)
s3ql.backends.common.CorruptedObjectError: Invalid metadata format: pickle
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/bin/mount.s3ql", line 9, in <module>
load_entry_point('s3ql==2.14', 'console_scripts', 'mount.s3ql')()
File "/usr/lib/s3ql/s3ql/mount.py", line 129, in main
(param, db) = get_metadata(backend, cachepath)
File "/usr/lib/s3ql/s3ql/mount.py", line 361, in get_metadata
seq_no = get_seq_no(backend)
File "/usr/lib/s3ql/s3ql/common.py", line 54, in get_seq_no
while ('s3ql_seq_no_%d' % seq_no) not in backend:
File "/usr/lib/s3ql/s3ql/backends/common.py", line 271, in __contains__
return self.contains(key)
File "/usr/lib/s3ql/s3ql/backends/comprenc.py", line 287, in contains
return self.backend.contains(key)
File "/usr/lib/s3ql/s3ql/backends/common.py", line 438, in contains
self.lookup(key)
File "/usr/lib/s3ql/s3ql/backends/common.py", line 107, in wrapped
return method(*a, **kw)
File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 279, in lookup
return self._extractmeta(resp, key)
File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 742, in _extractmeta
raise CorruptedObjectError('Invalid metadata format: %s' % format_)
s3ql.backends.common.CorruptedObjectError: Invalid metadata format: pickle
Which was to be expected, but a bit rude I think.
When I use 2.16 upgrade, I get the following message:
# s3ql.upgrade *****.******.******.*****
Getting file system parameters..
File system revision too old to upgrade!
You need to use an older S3QL version to upgrade to a more recent
revision before you can use this version to upgrade to the newest
revision.
The last S3QL version that supported this file system revision
was 2.13. To run this version's s3qladm, proceed along
the following steps:
$ wget http://s3ql.googlecode.com/files/s3ql-2.13.tar.bz2
|| wget https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.13.tar.bz2
$ tar xjf s3ql-2.13.tar.bz2
$ (cd s3ql-2.13; ./setup.py build_ext)
$ s3ql-2.13/bin/s3qladm <options>
2.13 says:
Getting file system parameters..
File system revision too old to upgrade!
You need to use an older S3QL version to upgrade to a more recent
revision before you can use this version to upgrade to the newest
revision.
The last S3QL version that supported this file system revision
was 2.12. To run this version's s3qladm, proceed along
the following steps:
$ wget http://s3ql.googlecode.com/files/s3ql-2.12.tar.bz2
|| wget https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.12.tar.bz2
$ tar xjf s3ql-2.12.tar.bz2
$ (cd s3ql-2.12; ./setup.py build_ext)
$ s3ql-2.12/bin/s3qladm <options>
2.12 runs smoothly, but warns:
It is strongly recommended to run the s3ql_verify command with the
--data option as soon as possible. This is necessary to ensure that the
upgrade to the next (2.11) S3QL release will run smoothly.
That's a totally rediculous statement, since 2.11 was before 2.12?
And finally, 2.12 to 2.14 runs smooth as well.
Pff... gonna be a rough ride upgrading my mailstore I see!
Regards,
Martin
On Tue, Sep 15, 2015 at 7:38 PM, Nikolaus Rath <[email protected]> wrote:
> On Sep 15 2015, Martin van Es <[email protected]> wrote:
>> On Mon, Sep 14, 2015 at 8:20 PM, Nikolaus Rath <[email protected]> wrote:
>>> On Sep 14 2015, Martin <[email protected]> wrote:
>>>> Hi Nikolaus
>>>>
>>>> On Monday, September 14, 2015 at 6:55:01 PM UTC+2, Nikolaus Rath wrote:
>>>>>
>>>>> On Sep 14 2015, Martin <[email protected] <javascript:>> wrote:
>>>>> Can you go to https://console.aws.amazon.com/s3/home and open the bucket
>>>>> that you're trying to upgrade? Please tell me the names of the objects
>>>>> in that bucket that start with 's3ql_metadata'.
>>>>>
>>>>
>>>> s3ql_metadata
>>>> s3ql_metadata_bak_0
>>>> s3ql_metadata_bak_1
>>>
>>> Uh? That's odd. Is that a test file system that you created just for the
>>> upgrade? There should be more files than that (at least one for every
>>> time you mounted+umounted the file system, but not more than 10).
>>
>> Yes, this is a fresh test fs and hasn't been (un)mounted many times.
>>
>>> For that file system, please copy & paste the full output of s3qladm
>>> upgrade from S3QL 2.9.
>>
>> # s3qladm --version
>> S3QL 2.9
>>
>> # s3qladm --cachedir /var/s3ql/ --authfile /var/s3ql/authinfo --no-ssl
>> upgrade s3://****.****.****.*****
>> Getting file system parameters..
>> Ignoring locally cached metadata for upgrade.
>>
>> I am about to update the file system to the newest revision.
>> You will not be able to access the file system with any older version
>> of S3QL after this operation.
>>
>> You should make very sure that this command is not interrupted and
>> that no one else tries to mount, fsck or upgrade the file system at
>> the same time.
>>
>>
>> Please enter "yes" to continue.
>>> yes
>> Metadata backup already exists, did something go wrong?
>
>
> Oh, sorry. I should have looked at the code first. It's not complaining
> about data in the bucket, but about data in your cache directory. Please
> use a clean --cachedir (or delete the files pertaining to your test
> bucket), and it should work.
>
>
> 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.
--
If 'but' was any useful, it would be a logic operator
--
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.
