good and bad news managa to upgrade 4 filesystems of 5
any tips what i can fix this?:
~# /root/s3ql/s3ql-2.17/bin/s3qladm --backend-options tcp-timeout=50
upgrade swift://xxxx
Getting file system parameters..
Using cached metadata.
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
Upgrading from revision 22 to 23...
Dumping metadata...
..objects..
..blocks..
..inodes..
..inode_blocks..
..symlink_targets..
..names..
..contents..
..ext_attributes..
Compressing and uploading metadata...
Wrote 611 KiB of compressed metadata.
Cycling metadata backups...
Backing up old metadata...
Uncaught top-level exception:
Traceback (most recent call last):
File "/root/s3ql/s3ql-2.17/bin/s3qladm", line 26, in <module>
s3ql.adm.main(sys.argv[1:])
File "/root/s3ql/s3ql-2.17/src/s3ql/adm.py", line 94, in main
options.cachedir))
File "/root/s3ql/s3ql-2.17/src/s3ql/adm.py", line 303, in upgrade
dump_and_upload_metadata(backend, db, param)
File "/root/s3ql/s3ql-2.17/src/s3ql/metadata.py", line 310, in
dump_and_upload_metadata
upload_metadata(backend, fh, param)
File "/root/s3ql/s3ql-2.17/src/s3ql/metadata.py", line 324, in
upload_metadata
cycle_metadata(backend)
File "/root/s3ql/s3ql-2.17/src/s3ql/metadata.py", line 123, in
cycle_metadata
cycle_fn("s3ql_metadata_bak_%d" % i, "s3ql_metadata_bak_%d" % (i + 1))
File "/root/s3ql/s3ql-2.17/src/s3ql/backends/comprenc.py", line 268, in
copy
self._copy_or_rename(src, dest, rename=False, metadata=metadata)
File "/root/s3ql/s3ql-2.17/src/s3ql/backends/comprenc.py", line 278, in
_copy_or_rename
(nonce, meta_old) = self._verify_meta(src, meta_raw)
File "/root/s3ql/s3ql-2.17/src/s3ql/backends/comprenc.py", line 134, in
_verify_meta
% (stored_key, key))
s3ql.backends.common.CorruptedObjectError: Object content does not match
its key (s3ql_metadata_bak_0 vs s3ql_metadata_bak_1)
root@vps:~# /root/s3ql/s3ql-2.17/bin/s3qladm --backend-options
tcp-timeout=50 upgrade swift://xxxx
Getting file system parameters..
Using cached metadata.
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
Upgrading from revision 22 to 23...
Uncaught top-level exception:
Traceback (most recent call last):
File "/root/s3ql/s3ql-2.17/bin/s3qladm", line 26, in <module>
s3ql.adm.main(sys.argv[1:])
File "/root/s3ql/s3ql-2.17/src/s3ql/adm.py", line 94, in main
options.cachedir))
File "/root/s3ql/s3ql-2.17/src/s3ql/adm.py", line 296, in upgrade
db.execute('ALTER TABLE inodes ADD COLUMN atime_ns INT NOT NULL DEFAULT
0')
File "/root/s3ql/s3ql-2.17/src/s3ql/database.py", line 98, in execute
self.conn.cursor().execute(*a, **kw)
File "src/cursor.c", line 990, in APSWCursor_execute.sqlite3_prepare
File "src/statementcache.c", line 386, in sqlite3_prepare
apsw.SQLError: SQLError: duplicate column name: atime_ns
root@vps179401:~# /root/s3ql/s3ql-2.17/bin/fsck.s3ql --backend-options
tcp-timeout=50 swift://xxxx
Starting fsck of swift://xxxx
Using cached metadata.
File system revision too old, please run `s3qladm upgrade` first.
root@vps:~#
--
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.
