Re: [s3ql] Problem after upgrading to s3ql 2.17.1

On Apr 11 2016, Chris Croome wrote: > Hi > > On a server running Debian stretch, after upgrading to 2.17.1 I tried to > upgrade the filesystem and got this error: The only upgrade paths that are guaranteed to work are from one minor S3QL release to the next (e.g. 2.16

Re: [s3ql] Re: Problem after upgrading to s3ql 2.17.1

Hi On Mon 11-Apr-2016 at 06:08:02AM -0700, Alexandre Gonçalves wrote: > > > > I looks that you didn't upgrade the filesystem itself The filesystem hasn't been upgraded as a fsck is needed first, but the fsck can't run as the filesystem hasn't been upgraded. At least that is my understanding.

[s3ql] Re: Problem after upgrading to s3ql 2.17.1

> > I looks that you didn't upgrade the filesystem itself Check the change log file. > -- 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

[s3ql] Problem after upgrading to s3ql 2.17.1

Hi On a server running Debian stretch, after upgrading to 2.17.1 I tried to upgrade the filesystem and got this error: s3qladm upgrade s3c://s.qstack.advania.com:443/crin4 Getting file system parameters.. Using cached metadata. File system is damaged, need to run fsck before upgrade.