On May 24 2016, Prakash Autade <[email protected]> wrote:
> Local metadata is corrupted. Remove or repair the following files manually
> and re-run fsck:
> /var/cache/s3/store/s3:=2F=2Fstore.db (corrupted)
> /var/cache/s3/store/s3:=2F=2Fstore.param (intact)
>
>
> For above, I visited thread
> <https://groups.google.com/forum/#!topic/s3ql/IDqeIocHTgs> and found that
> the solution is to (re)move local-metadata.
>
> But if I remove the local metadata, we will loss data of last 24hrs, which
> is not accepted in our case.
>
> can you please suggest,
>
> 1. How can I recover from local-corrupted-meta-data ?
You'll need to ask a real SQLite expert.
> 2. How can I prevent above situation?
Most likely by avoiding what caused it in the first place. Normally the
only way to corrupt the SQLite database is a hard crash, a corrupted
hard-drive, or damaged RAM. What prevented you from doing a clean
unmount?
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.
