On Apr 09 2020, Daniel Jagszent <[email protected]> wrote:
> Hi,
>
>> [...] I am not particularly concerned with losing 2 hours, but I am
>> very interested to know if this is the correct approach to have used,
>> or if there are better approaches.
>
> I would probably have spend some time to try to repair the local
> metadata. It's a SQLite <https://sqlite.org/index.html> database so
> installing the sqlite CLI and opening the database up with that tool can
> help most of the time. Downloading the metadata backups should be the
> very last resort.
> PS: do you upload metadata backups every hour (i.e. you changed
> --metadata-upload-interval)? Normally they get uploaded every 24 hours
> so you would loose up to two days, not two hours.
>
> The error from fsck (apsw.ConstraintError: UNIQUE constraint failed:
> contents.parent_inode, contents.name_id) means that you somehow had two
> files in a directory with the same name. I have no clue how that could
> have happened,
My guess is that it is simple corruption of the data. The original email
said that the server crashed. This means that the SQLite database can
get corrupted.
Best,
-Nikolaus
--
GPG 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/87imi8o7l6.fsf%40vostro.rath.org.
