I have an Odroid HC2 (arm32) that I recently upgraded to an HC4 (arm64). It’s running Armbian / OMV5.
When I run:
restic check --read-data-subset=1/128
The system grinds to a halt at this point:
using temporary cache in /tmp/restic-check-cache-082606718
created new cache in /tmp/restic-check-cache-082606718
create exclusive lock for repository
check all packs
check snapshots, trees and blobs
After the check snapshots, trees and blobs starts, about 2-3 minutes later the whole system becomes unresponsive and grinds to a halt. Previously, this command would run without problem and take about 30m.
At this point I (with difficulty) kill the restic task, unlock the repository and keep going.
I have successfully run:
restic forget --prune --keep-daily 7 --keep-weekly 6 --keep-monthly 18
The last two have been slow in comparison to how they used to run, but they complete. This is surprising given that the HC4 is considerably more powerful and with more RAM than the HC2. All the other tools I use in the system are running without a hitch.
In upgrading the system I did a complete reinstall of the OS, and migrated to the arm64 version of restic.
Any thoughts or suggestions for further diagnosing?