On Aug 09 2016, Andy Cress <[email protected]> wrote:
> One anomaly that I saw in the initial cache directory is some s3*
> files related to this gs* bucket.
>
> fsck.log s3:=2F=2Fcust-company=2Fcust-backup01=2F.db
> gs:=2F=2Fcust-backup01-cache s3:=2F=2Fcust-company=2Fcust-backup01=2F.params
> gs:=2F=2Fcust-backup01.db s3:=2F=2Fcust-company=2Fcust-backup01.db
> gs:=2F=2Fcust-backup01.params s3:=2F=2Fcust-company=2Fcust-backup01.params
> mount.log
>
> It seemed to me that the s3* metadata files were probably not valid,
> so first I made a tar of these files, and cleared the cache before
> applying the downloaded metadata. Should I restore some of those
> files before re-running the fsck?
No. You should be able to start with an empty cache directory, download
the metadata, and then run fsck.s3ql.
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.
