I have an old S3 filesystem, last used June 2017 (according to the timestamps in the files in the bucket). I'm trying to upgrade this so it can be mounted with current S3QL versions. I still have the s3qlauth.txt file (timestamp October 2017).
If I use s3ql version 2.21, which looks about the right vintage for the timestamps in the bucket and is most likely the version I used back then because it's the one in Debian, then I get: > s3ql.backends.s3c.S3Error: AllAccessDisabled: All access to this object has been disabled If I use s3ql version 2.24, which looks about the right vintage for the timestamp in the s3qlauth.txt file, then it just spins on: > Encountered BadDigestError (BadDigest: Meta MD5 for s3ql_passphrase does not match), retrying Backend.open_read (attempt 1)... 3.0 or any version fails with this message, which to me suggests a filesystem version mismatch: > s3ql.backends.common.CorruptedObjectError: Object content does not match its key (s3ql_metadata vs s3ql_metadata_bak_10) ...but it does at least manage to read the metadata files from the bucket, which means that my credentials work. Any suggestions how to get unstuck here? My suspicion is that Amazon's configuration changed somewhere, which is why 2.21 is failing. Is there any way to get the actual file system version from the metadata files? -- ┌─── http://www.cowlark.com ─── │ "I have always wished for my computer to be as easy to use as my │ telephone; my wish has come true because I can no longer figure out │ how to use my telephone." --- Bjarne Stroustrup -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/CALgV52jr%2B78of1RpXbgyH2vyBBZSqg5c9dAF50_COXnW5cFL3w%40mail.gmail.com.
