Eek! That's weird - I haven't explicitly upgraded either, just gone along with Ubuntu upgrades. I'm on Ubuntu 16.10, and have s3ql (2.15+dfsg-1), and python3-llfuse (1.1.1+dfsg-4), which are the versions that come with 16.10. (python-llfuse isn't installed). Is this a configuration issue in the Ubuntu package list?
Ubuntu 17.04 leaves the s3ql version the same, and upgrades python3-llfuse to 1.2+dfsg-1, but you said it needs to be *down*graded... is that even more wrong? Am I likely to make it worse if I upgrade to Ubuntu 17.04? A long time ago I installed s3ql from your PPA (but switched to Ubuntu's version at a point where they were almost the same), should I try that again? On Sunday, 7 May 2017 03:47:04 UTC+1, Nikolaus Rath wrote: > > Hi Ben, > > You probably updated python-llfuse to a version that's no longer > compatible with your S3QL version. Either upgrade the latter, or downgrade > the former. > > Best, > Nikolaus > > On May 6, 2017 1:21:50 PM PDT, Ben Hymers <[email protected] <javascript:>> > wrote: >> >> Oh no! I seem to be in a pickle. I set up backups using s3ql a long time >> ago (6 years according to my logs! Doesn't time fly). In that time I've >> upgraded Ubuntu (and s3ql) a number of times and upgraded the file system >> and it's been fine, but I just noticed that my backups have been failing >> since the last Ubuntu upgrade in October last year (and apparently the >> script I wrote to email me on failures is also failing, ironically). >> >> I upgraded from Ubuntu 16.04 to 16.10 on October 18th, to give some >> context to the dates in the logs below. As far as I understand, s3ql didn't >> actually get upgraded then so I'm not sure what's wrong! Perhaps the file >> system was still mounted when I started the upgrade? The relevant thing >> (the first sign of error) seems to be the "ValueError: No workers is not a >> good idea". How do I fix that, and how do I recover everything from this >> situation? >> >> I'm using an Amazon S3 backend. >> >> Here's what's happening. >> >> Trying to access mount point: >> >> me@server:~# cd /tmp/s3ql_backup_19842 >> bash: cd: /tmp/s3ql_backup_19842: Transport endpoint is not connected >> >> >> >> Trying to unmount: >> >> me@server:~# umount.s3ql /tmp/s3ql_backup_19842 >> File system appears to have crashed. >> >> >> >> Trying to fsck: >> >> >> me@server:~# fsck.s3ql s3://blah-blah-blah >> Can not check mounted file system. >> >> >> >> First error in mount.log: >> >> 2016-10-19 04:00:11.343 28133:MainThread s3ql.mount.determine_threads: >> Using 4 upload threads. >> 2016-10-19 04:00:11.371 28133:MainThread s3ql.mount.main: Autodetected >> 65492 file descriptors available for cache entries >> 2016-10-19 04:00:11.947 28133:MainThread s3ql.mount.get_metadata: Using >> cached metadata. >> 2016-10-19 04:00:11.950 28133:MainThread s3ql.mount.main: Setting cache >> size to 198255 MB >> 2016-10-19 04:00:11.966 28133:MainThread s3ql.mount.main: Mounting >> filesystem... >> 2016-10-19 04:00:12.066 28137:MainThread s3ql.daemonize. >> detach_process_context: Daemonizing, new PID is 28138 >> 2016-10-19 04:00:12.354 28138:MainThread s3ql.mount.unmount: Unmounting >> file system... >> 2016-10-19 04:00:12.355 28138:MainThread root.excepthook: Uncaught top-level >> exception: >> Traceback (most recent call last): >> File "/usr/bin/mount.s3ql", line 9, in <module> >> load_entry_point('s3ql==2.15', 'console_scripts', 'mount.s3ql')() >> File "/usr/lib/s3ql/s3ql/mount.py", line 214, in main >> llfuse.main(options.single) >> File "src/fuse_api.pxi", line 304, in llfuse.main (src/llfuse.c:34899) >> ValueError: No workers is not a good idea >> >> >> >> Relevant time period in fsck.log: >> >> 2016-10-19 04:00:08.023 28121:MainThread s3ql.fsck.main: Starting fsck >> of s3://blah-blah-blah/ >> 2016-10-19 04:00:10.223 28121:MainThread s3ql.fsck.main: Using cached >> metadata. >> 2016-10-19 04:00:10.296 28121:MainThread s3ql.fsck.main: File system is >> marked as clean. Use --force to force checking. >> 2016-10-20 04:00:08.170 15818:MainThread root.excepthook: Can not check >> mounted file system. >> 2016-10-21 04:00:07.653 15455:MainThread root.excepthook: Can not check >> mounted file system. >> >> >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -- 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.
