[Borgbackup] what are the implications of this repair?
Thomas Waldmann
tw at waldmann-edv.de
Wed Jul 18 05:49:45 EDT 2018
> In another repo I wasn't as lucky, the index files got corrupted, and
> instead of ~20 archives only one remained. The messages I got from check
> --repair are like:
>
> Analyzing archive photos-2018-05-31T03:57-07:00 (7/17)
> Archive metadata block is missing!
That likely means you missed or corrupted files in repo/data/...
Did you check the hardware (see our docs about IntegrityErrors).
> After the check-repair this is one of the repos that is no longer listed
> by "borg list". Do I gather correctly that there is no way to
> reconstruct those indexes?
It's archive metadata (list of all blocks that store information about
backed up filenames, file metadata, lists of file content block
references), not just an index/cache.
> And at what point does all the data that is
> no longer referenced get garbage collected, I presume that happens the
> next time I run borg prune?
No, iirc it should be in check --repair already.
prune is just a time-based delete.
--
GPG ID: 9F88FB52FAF7B393
GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
More information about the Borgbackup
mailing list