-
-
Notifications
You must be signed in to change notification settings - Fork 810
Description
I have a borg archive with a size of ~3TB. The oldest backup is from 2018 and compact was never executed on it, only create, extract and prune. Executing check on it returns no error. I still have a ZFS snapshot of that archives state.
Current borg version is 1.2.8 and has always been installed and updated from the ubuntu repos.
I discovered, that there is some data in the backups that shouldnt be there, so I ran recreate on it with some path exclusions. After, I executed compact. Both executions finished without error (but took a long time (> 24h each)).
Then I executed borg check --progress --verify-data and because errors have been found, I executed borg check --repair --progress --verify-data. This is the output still visible in the screen, it executed it in:
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
<Verifying data 21.90% 108 orphaned objects found!
Archive consistency check complete, problems found.
I'm not sure what this means:
- Do I still have problems and should I run check --repair again?
- Is the only problem that compact has forgotten some objects which then were deleted by check --repair?
Furthermore, can I do something to help fix a potential problem (since I still have the ZFS snapshot of before), like
- running check after recreate and before compact to check where errors occur?
- rerun check and/or recreate on any stage with flags like verbose?