Hello,
I need to upgrade an old installation of S3QL version 1.19.
I've found an old topic
<https://groups.google.com/forum/#!topic/s3ql/mYVW_86roC4> here in the
group that suggest to upgrade first to 2.8 and the to 2.10, 2.13 and so on.
Then I've started with this path, I've updated to 2.8 and run s3qladm
upgrade with success, I've then installed 2.10 and upgraded again, then
I've tried 2.12 and it says that there is no upgrade needed (this was
aspected):
Getting file system parameters..
Using cached metadata.
File system already at most-recent revision
Then I've tried with 2.13 and I got this error:
Getting file system parameters..
Wrong file system passphrase
I'm sure that passhphrase was right, nobody changed my authinfo2 file and
there wasn't any kind of operation that can have changed the passphrase.
I've then dowgraded to 2.12 and tried to mount the file system but
immediatly it had crashed with this error:
2017-05-23 12:55:10.697 26671:MainThread s3ql.mount.determine_threads:
Using 2 upload threads.
2017-05-23 12:55:10.698 26671:MainThread s3ql.mount.main: Autodetected
65498 file descriptors available for cache entries
2017-05-23 12:55:36.010 26671:MainThread s3ql.mount.get_metadata:
Downloading and decompressing metadata...
2017-05-23 12:55:36.265 26671:MainThread s3ql.mount.get_metadata: Reading
metadata...
2017-05-23 12:55:36.267 26671:MainThread s3ql.metadata.restore_metadata:
..objects..
2017-05-23 12:55:36.332 26671:MainThread s3ql.metadata.restore_metadata:
..blocks..
2017-05-23 12:55:36.433 26671:MainThread s3ql.metadata.restore_metadata:
..inodes..
2017-05-23 12:55:36.611 26671:MainThread s3ql.metadata.restore_metadata:
..inode_blocks..
2017-05-23 12:55:36.719 26671:MainThread s3ql.metadata.restore_metadata:
..symlink_targets..
2017-05-23 12:55:36.720 26671:MainThread s3ql.metadata.restore_metadata:
..names..
2017-05-23 12:55:36.853 26671:MainThread s3ql.metadata.restore_metadata:
..contents..
2017-05-23 12:55:37.052 26671:MainThread s3ql.metadata.restore_metadata:
..ext_attributes..
2017-05-23 12:55:37.085 26671:MainThread s3ql.mount.main: Mounting
filesystem...
2017-05-23 12:55:37.109 26730:MainThread
s3ql.daemonize.detach_process_context: Daemonizing, new PID is 26732
2017-05-23 12:55:37.170 26732:MainThread s3ql.mount.unmount: Unmounting
file system...
2017-05-23 12:55:37.170 26732:MainThread root.excepthook: Uncaught
top-level exception:
Traceback (most recent call last):
File "/bin/mount.s3ql", line 9, in <module>
load_entry_point('s3ql==2.12', 'console_scripts', 'mount.s3ql')()
File
"/usr/lib64/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/mount.py",
line 215, in main
llfuse.main(options.single)
File "src/fuse_api.pxi", line 304, in llfuse.main (src/llfuse.c:35376)
ValueError: No workers is not a good idea
fsck says that the file system was fine but any attempt to mount it has
failed with the "No workers" error.
I've not tried to mount with 2.9 and 2.10, I've just run the upgrade and
fsck to check that everything was fine.
I was in a production environment so I had to make the FS online asap, then
I've downgraded to 1.19, restored the metadata and mount back the file
system with the old previous version of s3ql.
I can try again the upgrade in next days, before doing this do you have any
suggestion? What is the recommended upgrade path for upgrade from 1.19 to
latest version (2.21)?
Thanks in advance for your help
Regards
Fabio Grasso
--
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.
