On Aug 08 2016, Andy Cress <[email protected]> wrote:
> I encountered this problem on one particular bucket and cannot seem to
> recover the s3ql filesystem. This system had been running for some
> time with s3ql-1.17 just fine, but now is stuck. I'm hoping that you
> can tell me how to use the backup metadata to get it going again.
[...]
>
> I did notice that s3qladm download-metadata failed (with the same
> primary key error) for no 0, but succeeds for no 1 below. I’m
> thinking that perhaps I can upload the s3ql_metadata_bak_0 instead of
> s3ql_metadata_bak, but if so, I need to know the procedure for that.
Have you tried to simply run fsck.s3ql after s3qladm download-metadata?
This should make fsck.s3ql to use the copy that you manually downloaded before.
Just make sure to use the same cache directory.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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.
