Hello David,
> I have an old S3 filesystem [...] I'm trying to upgrade this so it can
> be mounted with current S3QL versions.[...]
> 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
where do you get this error? (Full debug log, backtrace) The bucket you
are trying to access is locked down; see
https://stackoverflow.com/questions/53329023/allaccessdisabled-all-access-to-this-object-has-been-disabled-error-being-thr

You should be able to mount your file systems with S3QL versions up to
version 2.26. After version 2.26 the file system changed (REV 23 to REV
24; see
https://groups.google.com/forum/#!msg/s3ql/4TzCVIMkA4o/xDxoKWCDAgAJ;context-place=forum/s3ql
<https://groups.google.com/forum/#%21msg/s3ql/4TzCVIMkA4o/xDxoKWCDAgAJ;context-place=forum/s3ql>)
and you need to upgrade the file system (
https://www.rath.org/s3ql-docs/adm.html#upgrading-the-file-system )
before you can mount it.

The current version of S3QL still uses REV 24 of the file system ( see
https://github.com/s3ql/s3ql/blame/master/src/s3ql/__init__.py#L46 ) so
you should be able to just install version 3.3.2 and do a file system
upgrade before you first mount it (that's why you got the
CorruptedObjectError exceptions)


-- 
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/66571ebe-726b-6cf7-6012-3a01e20dfba2%40jagszent.de.

Reply via email to