Pablo J <[email protected]> writes:
> Hi!
>
> I'm using s3ql ver. 2.11.1 under Debian. My vps provider unfortunately
> restarted my machine while some resources were still mounted
> there. Now fsck says my local metadata is corrupted and remote is
> outdated:
>
> Using cached metadata.
> Remote metadata is outdated.
> Checking DB integrity...
> wrong # of entries in index sqlite_autoindex_blocks_1
> Local metadata is corrupted. Remove or repair the following files manually
> and re-run fsck:
> /root/.s3ql/swift:=2F=2F###EDITED###=2Fs3ql=2Fbackup.db (corrupted)
> /root/.s3ql/swift:=2F=2F###EDITED###=2Fs3ql=2Fbackup.param (intact)
>
> What's the action I should take now. I'd like to minimize the data
> loss if possible.
Unless you have an SQLite expert at hand who is willing to (try to)
repair the database, your only option is to delete (or better, move to a
different location just in case) the local metadata. This will force
fsck.s3ql to use the most-recent remote metadata.
By default, metadata is uploaded every 24h, so in the worst case you
could loose data from the last 24th. But this can be customatized by the
--metadata-upload-interval option for mount.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.
