Problems mounting upgraded filesystem

[Xomex]

I've happily been using s3ql for many years and across many versions. With backends currently on Amazon, Wasabi, and Google, using s3://  s3c:// and gs://

With the recent release of V5.0.0 I upgraded all the backend filesystems according to the docs. This seemed to go smoothly although my internet has been a bit flaky lately.

Now, I can't mout the upgraded filesystems getting the dreaded:

"ERROR: File system revision too old, please run `s3qladm upgrade` first."

fsck.s3ql --force works fine on all systems, takes a while but completes without error.

What's the most likely problem here and how to fix it? Is it possible the something local is stale or didnt get completed in the filesystem upgrade?

Appreciate any help or suggestions. Thanks.

[Nikolaus Rath]

Hi,

Thanks for the report! A few questions:

• Does it work if you try with a different (empty) cache directory?
  
• Can you reproduce the problem with a new filesystem (created with a previous release)?
  

Best,

Nikolaus

--

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+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/e630983c-a624-48c1-b18b-38f9e5133a22n%40googlegroups.com.

[Xomex]

Yes, mounting with a new (empty) cachdir downloaded new healthy metadata and solved all problems.

Thanks again for the timely assistance :-)