Can't Upgrade Filesystem from 3.2.2 to 6.3

[toffer...@gmail.com]

Hi,

I have an old bucket on DreamObjects containing what I believe is an S3QL 3.2.2 filesystem. When I try to access it with S3QL 6.3, I get: "ERROR: File system revision needs upgrade (or backend data is corrupted)". The same error occurs when I run s3qladm upgrade.

A few relevant details:

• DreamObjects changed their server name and my bucket name, and I've updated both in my S3QL config accordingly.
• There's a chance some data may have been lost over the 4 years since I last accessed this filesystem.
• I tried downgrading to S3QL 4.0.1, thinking S3QL might only support upgrading from the immediately previous version. However, S3QL 4.0.1 only supports V2 signatures, while DreamObjects' current server apparently only supports V4 (https://help.dreamhost.com/hc/en-us/articles/360001370846-What-DreamObjects-hostname-should-I-use-to-connect).

So I'm stuck: S3QL 4 can't reach DreamObjects due to the new signature requirement, and S3QL 6 can't upgrade the old 3.2.2 filesystem.

Does anyone have suggestions for a way forward? I'm hoping I've just missed something.

Thank you for any help!

[Nikolaus Rath]

"toffer...@gmail.com" <toffer...@gmail.com> writes:

> Hi,
>
> I have an old bucket on DreamObjects containing what I believe is an S3QL
> 3.2.2 filesystem. When I try to access it with S3QL 6.3, I get: "ERROR:
> File system revision needs upgrade (or backend data is corrupted)". The
> same error occurs when I run s3qladm upgrade.
>
> A few relevant details:
>

> - DreamObjects changed their server name and my bucket name, and I've

> updated both in my S3QL config accordingly.

> - There's a chance some data may have been lost over the 4 years since I
> last accessed this filesystem.
> - I tried downgrading to S3QL 4.0.1, thinking S3QL might only support

> upgrading from the immediately previous version. However, S3QL 4.0.1 only
> supports V2 signatures, while DreamObjects' current server apparently only
> supports V4 (
> https://help.dreamhost.com/hc/en-us/articles/360001370846-What-DreamObjects-hostname-should-I-use-to-connect
> ).
>
> So I'm stuck: S3QL 4 can't reach DreamObjects due to the new signature
> requirement, and S3QL 6 can't upgrade the old 3.2.2 filesystem.
>
> Does anyone have suggestions for a way forward? I'm hoping I've just missed
> something.

If that's the situation, then I think the only solution for you would be
to backport v4 signature support to S3QL 4, or to re-add upgrade
capabilities from 3.2 to S3QL 6.3. The former is probably easier.

Best,
Nikolaus