Be aware when you update from 2.15 you cannot go back (even use anymore the
2.15 binary)
REASON:
upgrade packets, upgrade/install llfuse 1.0 <-- This will *break totally
s3ql-2.15* version mount. if you do that you *CANNOT MOUNT* anymore on old
version. so be sure you know what you doing.
lucly fsck 2.15 works with llfuse so you can get clean filesystem after
messing up!
Logs what happen when you try mount it with old version:
2016-03-09 21:19:32.768 22255:MainThread root.excepthook: Uncaught
top-level exception:
Traceback (most recent call last):
File "/root/s3ql/s3ql-2.15/bin/mount.s3ql", line 26, in <module>
s3ql.mount.main(sys.argv[1:])
File "/root/s3ql/s3ql-2.15/src/s3ql/mount.py", line 214, 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
after this it dies.
Only way is upgrade everything, compile 2.17 s3ql.
then one by one umount old 2.15 and upgrade filesystem 2.17. remember when
you doing this there is no going back.
*There is one more side effect of installing llfuse:*
when using old 2.15 you will get this errors after installing llfuse. you
need use option to raise timer.
Encountered ConnectionTimedOut (send/recv timeout exceeded), retrying
Backend._copy_helper (attempt ...
--
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.
