Good news: I solved the problem with packages that I found at http://snapshot.debian.org/package/s3ql/2.15%2Bdfsg-1/ (It took several searches to find this repository, because Ubuntu package search does not know these packages, and also it takes kind of insider knowledge that these debian packages will usually work with Ubuntu.)
Maybe this repository could be mentioned in the frequently asked questions, as I found several discussions on the web where the same issue appeared. This situation appeared because the upgrade was running while the filesystem was mounted (upgrade via PPA). As a result the filesystem became unusable and un-rescue-able. Would it be feasible if the upgrade asks whether to unmount with the old version before doing the upgrade if it detects a mounted partition? Best, Peter On Sunday, May 7, 2017 at 9:10:39 AM UTC+3, Peter Schüller wrote: > > I now have the same problem and I need the 2.16 version for ubuntu Trusty > 14.04 but I cannot find it as a ubuntu package because I had it installed > it from the PPA and there is no ubuntu package for 2.16 available for > download (or I did not find it). > > Building 2.16 from source on my xenial ubuntu 16.04 using the mercurial > repo worked but the installation fails because llfuse version is 1.0 in > xenial and 2.16 requires < 1.0. > > The server where I need the package has not enough resources to build the > repo. > > Can I find a binary release of 2.16 somewhere to do fsck and then upgrade > the file system version? > > Is there another trick to convince the 2.18 version to do a fsck on the > 2.16 filesystem revision? > > Best, > Peter > > On Tuesday, July 31, 2012 at 3:59:00 AM UTC+4, danalstadt wrote: >> >> I'm getting a few errors, and the resolution seems to be circular: >> >> $ mount.s3ql s3://[bucket-name] /mnt/[bucket-name]/ >> Using 2 upload threads. >> Using cached metadata. >> File system revision too old, please run `s3qladm upgrade` first. >> >> But when I try to upgrade: >> >> $ s3qladm upgrade s3://[bucket-name] >> Getting file system parameters.. >> Using cached metadata. >> File system damaged, run fsck first! >> >> Then, when I try to fsck as suggested: >> >> $ fsck.s3ql s3://[bucket-name] >> Using cached metadata. >> Remote metadata is outdated. >> File system revision too old, please run `s3qladm upgrade` first. >> >> >> What to do? I'm using s3ql 1.11.1. >> > -- 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.
