On May 23 2017, Fabio Grasso <[email protected]> wrote:
> 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
This is odd... are you sure about that?
> 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: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
This is because you didn't downgrade python-llfuse at the same time.
> 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)?
I'd say go to 2.12 for now, and then let's figure out things from
there.
Best,
-Nikolaus
--
GPG 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.
