check --repair fails with exception and OSError: [Errno 19] No such device #9211
Unanswered
DonkeeeyKong
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Well, mmap is not working, that's unexpected because it usually works.
I will check if there were any relevant changes to mmap usage after 1.2.4:
Check that (comment right above where it crashed): Update: no, there is code right above that, that avoids 0 byte files. So, guess you have something unusal there, mmap usually works on Linux. Maybe that mergerfs? You could try copying that repo to a known-good filesystem (like ext4 or zfs or ...) and known-good disk and try repairing it there. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
On my NAS I have nightly Borg Backups to a mergerfs pool. A few days ago those failed with
OSError: [Errno 30] Read-only file system. One of the drives had a very highUDMA_CRC_Error_Count, so I switched the cable and the drive has been working fine since.fsckshowed no problems either, an extended S.M.A.R.T test was fine and theUDMA_CRC_Error_Counthasn't gone up anymore. My backups have been working fine now, except one which fails withborg.helpers.errors.IntegrityError: Data integrity error: Invalid segment entry size 2685978130 - too big [segment 13115, offset 88836055].Now, when I run
borg checkit shows some errors:It is not possible to
check --repairthe repository though:Any ideas what's happening here and what I can do to save that repository?
Any help is welcome. Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions