[Borgbackup] "borg check --repair" problem

[Joseph Hesse]

Hi,

I did a "borg check" on my repository and got 279 error lines, each of 
the form:

ID: 024126ba2e8883b2c36b505fa2217a80479e4334faa659b4a4ff09918e316a5c 
rebuilt index: <not found>      committed index: (417, 455027472)
  ending with : "Completed repository check, errors found."

I am using Linux with ext4 file system and the partition on the external 
drive passed an "fsck" and "badblocks" test.

I deleted the index for the repository and then did a "borg check 
--repair",  and, even though there was a warning that this was an 
experimental feature,
I felt I had no other choice but to proceed.  I got the output below.
There a 3 backups in this output and since the files in question that 
are causing the error have very long names, I have replaced them with 
FILE1, FILE2, ..., FILE6 and changed user names.

I plan on deleting the 3 backups in the repository and hope for the 
best.  Is this a good plan?  I prefer not but I can afford to lose the 
entire repository since I have Borg backups on other repositories.

Thank you,
Joe


user at Laptop ~]$ borg check --repair /borg/repo/ISBorgBackup/
'check --repair' is an experimental feature that might result in data loss.
Type 'YES' if you understand this and want to continue: YES
Data integrity error: Segment entry checksum mismatch [segment 417, 
offset 33880751]
Enter passphrase for key /borg/repo/ISBorgBackup:
user-2020-06-30T18:02:21: FILE1: New missing file chunk detected (Byte 
1497238-3698398). Replacing with all-zero chunk.
user-2020-06-30T18:02:21: FILE2: New missing file chunk detected (Byte 
1878467-3580233). Replacing with all-zero chunk.
user-2020-06-30T18:02:21: FILE2: New missing file chunk detected (Byte 
4421386-6930565). Replacing with all-zero chunk.
user-2020-06-30T18:02:21: FILE3: New missing file chunk detected (Byte 
3382479-4869362). Replacing with all-zero chunk.
user-2020-06-30T18:02:21: FILE4: New missing file chunk detected (Byte 
4865467-6609832). Replacing with all-zero chunk.
user-2020-06-30T18:02:21: FILE5: New missing file chunk detected (Byte 
2085016-5899534). Replacing with all-zero chunk.
user-2020-06-30T18:02:21: FILE6: New missing file chunk detected (Byte 
4148719-5052114). Replacing with all-zero chunk.

user-2020-07-15T22:07:36: FILE1: New missing file chunk detected (Byte 
1497238-3698398). Replacing with all-zero chunk.
user-2020-07-15T22:07:36: FILE2: New missing file chunk detected (Byte 
1878467-3580233). Replacing with all-zero chunk.
user-2020-07-15T22:07:36: FILE2: New missing file chunk detected (Byte 
4421386-6930565). Replacing with all-zero chunk.
user-2020-07-15T22:07:36: FILE3: New missing file chunk detected (Byte 
3382479-4869362). Replacing with all-zero chunk.
user-2020-07-15T22:07:36: FILE4: New missing file chunk detected (Byte 
4865467-6609832). Replacing with all-zero chunk.
user-2020-07-15T22:07:36: FILE5: New missing file chunk detected (Byte 
2085016-5899534). Replacing with all-zero chunk.
user-2020-07-15T22:07:36: FILE6: New missing file chunk detected (Byte 
4148719-5052114). Replacing with all-zero chunk.

user-2020-07-19T16:35:57: FILE1: New missing file chunk detected (Byte 
1497238-3698398). Replacing with all-zero chunk.
user-2020-07-19T16:35:57: FILE2: New missing file chunk detected (Byte 
1878467-3580233). Replacing with all-zero chunk.
user-2020-07-19T16:35:57: FILE2: New missing file chunk detected (Byte 
4421386-6930565). Replacing with all-zero chunk.
user-2020-07-19T16:35:57: FILE3: New missing file chunk detected (Byte 
3382479-4869362). Replacing with all-zero chunk.
user-2020-07-19T16:35:57: FILE4: New missing file chunk detected (Byte 
4865467-6609832). Replacing with all-zero chunk.
user-2020-07-19T16:35:57: FILE5: New missing file chunk detected (Byte 
2085016-5899534). Replacing with all-zero chunk.
user-2020-07-19T16:35:57: FILE6: New missing file chunk detected (Byte 
4148719-5052114). Replacing with all-zero chunk.
Archive consistency check complete, problems found.