On Mon, Sep 14, 2015 at 8:20 PM, Nikolaus Rath <[email protected]> wrote: > On Sep 14 2015, Martin <[email protected]> wrote: >> Hi Nikolaus >> >> On Monday, September 14, 2015 at 6:55:01 PM UTC+2, Nikolaus Rath wrote: >>> >>> On Sep 14 2015, Martin <[email protected] <javascript:>> wrote: >>> Can you go to https://console.aws.amazon.com/s3/home and open the bucket >>> that you're trying to upgrade? Please tell me the names of the objects >>> in that bucket that start with 's3ql_metadata'. >>> >> >> s3ql_metadata >> s3ql_metadata_bak_0 >> s3ql_metadata_bak_1 > > Uh? That's odd. Is that a test file system that you created just for the > upgrade? There should be more files than that (at least one for every > time you mounted+umounted the file system, but not more than 10).
Yes, this is a fresh test fs and hasn't been (un)mounted many times. > For that file system, please copy & paste the full output of s3qladm > upgrade from S3QL 2.9. # s3qladm --version S3QL 2.9 # s3qladm --cachedir /var/s3ql/ --authfile /var/s3ql/authinfo --no-ssl upgrade s3://****.****.****.***** Getting file system parameters.. Ignoring locally cached metadata for upgrade. I am about to update the file system to the newest revision. You will not be able to access the file system with any older version of S3QL after this operation. You should make very sure that this command is not interrupted and that no one else tries to mount, fsck or upgrade the file system at the same time. Please enter "yes" to continue. > yes Metadata backup already exists, did something go wrong? Regards, Martin -- 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.
