Nikolaus, On Tue, Aug 9, 2016 at 6:51 PM, Nikolaus Rath <[email protected]> wrote: >>> 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. >> >> Aha, that does proceed, but it looks like it is deleting nearly every >> s3ql_data_ block with 'Deleted spurious object nnn', so I interrupted >> it. Debug shows a sequence like that below, repeated. Is this >> ok/valid? > > Everything that you have created after the metadata backup was created > is expected to be treated as spurious and deleted (since S3QL has no way > to map it to files). Does that make sense, given the age of the metadata > backup that you downloaded? > >> Is there a way to validate the metadata? > > Yes, fsck.s3ql :-).
I went ahead and finished the fsck.s3ql and it found about 700 consecutive spurious blocks, put a number of files in lost+found, but did recover the filesystem. Something strange must have happened to get it corrupted this badly. This symptom is pretty rare from what I have experienced so far, across a variety of s3ql cloud storage cases. Thanks for your help. Andy -- 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.
