New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Fixable data integrity errors? #8187
Comments
It seems that you have issues in very old segment files (5, 7, 28, ...) and also in maybe recent segment files (18080). That looks quite bad and strange. Ideas:
|
This could be the case, but I hope not. Other old files, in the same partition, besides borg, still seem to be good. Unfortunately, I have never run the check before.
Since the error, I have not changed anything on the backup and have not added a new one. The best I can do now is start a edit2: edit3:
I never run a |
Errors can also come from HW and SW malfunctioning, like RAM or CPU issues, maybe the storage controller or even cables. Kernel and filesystem could also be the culprit. As long as there is such an error source present (e.g. bad RAM), borg check --repair could do more harm than good. Orphaned objects are harmless (== chunks that are not used by any archive) and nothing to worry about. |
@ThomasWaldmann log `borg check --repair`
Doe's it make sense to let it run? Or do I waste my time? |
There is quite a lot of corruption in these segment files. That checksum (CRC32) should be always correct. So either you had a systematic read problem when copying the files to the new location or the on-disk content on the old location is already badly corrupted. It's hard to say whether it makes sense to continue, because one can not easily know how your backups are distributed over the segments or how much percentual damage there is. But there is a lot of damage. BTW, when upgrading to borg > 1.2.4 you must read and follow the important note at the top of the changelog. In your case, I guess you should not try to upgrade (1.2.4 would be fine though) and fix your repo issues at the same time. The checksum mismatches are not related to the upgrade though. |
Thank you for everything!
https://github.com/borgbackup/borg/blob/1.2.4/docs/changes.rst#version-124-2023-03-24 |
You also need to follow these notes when upgrading 1.2.x (x <=4) to 1.2.y (y > 4). |
Hi folks,
I recently had a hardware failure in one of my servers. The HDDs probably had power failures from time to time, because there was too high a load on one lane of the power supply (presumably). Unfortunately this went on for 2 days.
Afterwards I was able to restore the RAID5 partition with 3 of 4 (plus a spare), so far ok. I then mounted the other two HDDs again and waited until the resync was finished. Unfortunately,
fsck
still showed many errors that could not be completely rectified:(it doesn't matter whether I say yes or no, the errors remain)
The
borg check
is also not very successful:Is there a possibility to find all backup points that are still without problems and delete the rest?
System:
Thank you very much!
The text was updated successfully, but these errors were encountered: