[Borgbackup] Full repository check, errors found: Index object count mismatch.

[Thomas Gries]

Am 19.04.24 um 01:11 schrieb Thomas Waldmann:
>> borg 1.2.7
>>
>> Today I ran the "Prüfen" Function (verify) in vorta and got for some
>> unknown reason "ERROR - Index object count mismatch".
>> What can I do? What is the suggested action I should do?
>
> If the repo was created and used with a borg version < 1.2.5, you MUST
> first read and follow the repo upgrade steps at the top of the 1.2.7
> changelog:
>
> https://borgbackup.readthedocs.io/en/1.2.7/changes.html#pre-1-2-5-archives-spoofing-vulnerability-cve-2023-36811
>
>
> After that, run borg check --repair on the repo.
>
>


thanks; problem *_solved_*.


Vorta reports now:
Check completed. INFO: Archive consistency check completed, no problems
found.)


*Feedback and two suggestions for improvement to you, Thomas:*


SUGGESTION 1:

* the borg check -repair function ends in my case with:

    1 orphaned objects found!
    Archive consistency check complete, problems found.
    (see below)


Here I suggest in cases like mine - when check -repair actually repaired
something - to add saying "*and repaired 1 problem"*

    1 orphaned objects found.
    Archive consistency check complete, problems found*and repaired 1
    problem.*



SUGGESTION 2:

In borgbackup >= 1.2.6 add a text explaining the most like reason and fix
*"check information on
https://borgbackup.readthedocs.io/en/1.2.7/changes.html#pre-1-2-5-archives-spoofing-vulnerability-cve-2023-36811"*

for error message
2024-04-18 20:20:17,066 - vorta.borg.borg_job - ERROR - Index object
count mismatch.

add
2024-04-18 20:20:17,066 - vorta.borg.borg_job - ERROR - Index object
count mismatch*(check information on
https://borgbackup.readthedocs.io/en/1.2.7/changes.html#pre-1-2-5-archives-spoofing-vulnerability-cve-2023-36811
)


*Regards
Tom

------------------------------------------------------------------------

Log (excerpt):

BORG_WORKAROUNDS=ignore_invalid_archive_tam borg info --debug
/media/benutzer/borg2tb/samosbackup 2>&1 | grep TAM | grep -i manifest^C


    samos-20230211-0038 Sat, 2023-02-11 00:38:09 tam:verified
    samos-20230331-0232 Fri, 2023-03-31 02:32:53 tam:verified
    samos-20230410-0902 Mon, 2023-04-10 09:02:16 tam:verified
    samos-20230519-1133 Fri, 2023-05-19 11:34:02 tam:verified
    samos-20230611-2239 Sun, 2023-06-11 22:39:54 tam:verified
    samos-20230718-1056 Tue, 2023-07-18 10:56:20 tam:verified
    samos-20230827-2352 Sun, 2023-08-27 23:52:56 tam:verified
    samos-20230907-1840 Thu, 2023-09-07 18:40:02 tam:verified
    samos-20231024-1101 Tue, 2023-10-24 11:01:45 tam:verified
    samos-20231230-2357 Sat, 2023-12-30 23:57:12 tam:verified
    samos-20240125-1958 Thu, 2024-01-25 19:58:32 tam:verified
    samos-20240224-2311 Sat, 2024-02-24 23:11:56 tam:verified
    samos-20240325-0923 Mon, 2024-03-25 09:23:03 tam:verified
    samos-20240414-2316 Sun, 2024-04-14 23:16:02 tam:verified
    samos-20240418-1235 Thu, 2024-04-18 12:35:21 tam:verified^C

borg check --repair /media/benutzer/borg2tb/samosbackup/


    This is a potentially dangerous function.
    check --repair might lead to data loss (for kinds of corruption it
    is not
    capable of dealing with). BE VERY CAREFUL!

    Type 'YES' if you understand this and want to continue: YES

(Enter passphrase for key:)

    1 orphaned objects found!
    Archive consistency check complete, problems found.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20240419/47d5fd9d/attachment.html>