borgbackup
Unable to distinguish if borg is working as intended or has frozen
I'm at 24 hours into my 7TB borg check -v --verify-data. This is relating to trying to figure out if there's an issue with my archive, as I was trying to diagnose which files had issues when are extracted from this repo. https://github.com/borgbackup/borg/issues/8994
> Starting repository check
> finished segment check at segment 15552
> Starting repository index check
> Index object count match.
> Finished full repository check, no problems found.
> Starting archive consistency check...
Given I gave the -v flag I was hoping something would be displayed every few hours at a minimum. At least with the starting repository check, we could tell from disk activity that something was happening. Maybe I just ran this with inappropriate settings, but it seems that since there is no way of showing any progress or glimpse of activity, it's impossible to know if this is working as intended or should be killed. Given that it's using 0% cpu as well is a bit concerning.
The ubuntu server this is running on with a borgmatic docker container, but i'm running the borg command directly borg check -v --verify-data /mnt/buan/bu/an-backup.borg
It's a 12th Gen Intel(R) Core(TM) i5-12500 CPU w/ a 9TB HDD that gets around 200MB/s r/w.
Looks like it successfully finished the repository part of the check and also the index looked good. That already means that it could read all segment files in the repo and the CRC32 check of their entries was also ok.
The archives part of the check checks all archives (how many do you have?). As you have given --verify-data it will not only check presence of referenced data, but also do a cryptograhic verification of all data referenced by the archives. There should be CPU usage and I/O while doing this.
Maybe do a local experiment with a relatively small repo so that you get a feeling of how borg check normally behaves.
BTW, at the start of the archives part of the check, borg 1.x will ask you for the borg key passphrase (except if the repo encryption mode is none).
For big repos, it is good to put the passphrase into BORG_PASSPHRASE env var so that it won't have to interactively prompt you for the passphrase.
I ran a 5TB check on a different repo, both that and this one only have one archive. That completed in 8 hours. Similar file counts and sizes. That's why I'm a little surprised it's still running 24hrs later on this one.
So while this is concerning, I'm guessing it won't reveal any new information on why I got rc 104 before, so I should probably just abandon this, and run --list like you said in the other thread to diagnose what the file issues in the archive were?
Especially it would be good to have full borg log output. All you showed yet is borgmatic log output and that didn't contain much information about the issue.
borg extract --list will result in a full file list logged, but even without that, borg usually logs useful warnings and errors.