[Borgbackup] Get know which files are damaged by: Data integrity error: Segment entry checksum mismatch

[Thomas Waldmann]

> Data integrity error: Segment entry checksum mismatch [segment 90,
> offset XXX]

90 is the segment number and also the file name of the affected file.
have a look into repo_dir/data/... and you'll see.

> 1. Is it possible to divide "borg check" into smaller "chunks" to do not
> have to wait long hours to get a result (and just run it with a given
> number of that smaller part - of course assuming to keep the repository
> itself untouched in the mean time)?

borg 1.1 supports this:
- --repository-only (only check repo, low-level)
- --archives-only (only check archives, high-level)

borg 1.2 (not released yet) will support:
- --max-duration (to limit how long it runs at a time, splitting the
whole check into multiple runs. in this mode, it ONLY does the crc32
segment file entry check)

> 2. Would performing the backup again "fix" the problem (assuming the
> reason of data corruption is detected and fixed before that operation)
> or I need to "repair" it before?

Guess you need to first find and fix the root cause of the corruption
(e.g. fix your hardware), then do a borg check --repair.

Whether this is a case of data loss in the repo has to be seen, this
depends on whether the issue is permanent or intermittent.

-- 

GPG ID: 9F88FB52FAF7B393
GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393