borg extract: check behaviour on integrity (or other) errors
Open
cmd: extract
enhancement
- Dominant language
- Python
- Stars
- 13.7k
- Forks
- 875
- Avg merge
- 11h 15m
- Merged PRs (30d)
- 192
Description
Assuming there is some issue in the repo storage, like partial corruption, unreadable disk sectors or so - how does borg handle them?
It might be the case that borg extract currently aborts when it hits such a file. More helpful would be to log an error for that file and try to continue. At the end, exit with warning status (1). This is similar to what borg does when creating archives and it encounters problems for single files.
Contributor guide
Assessment
This issue has not been assessed yet.