-
-
Notifications
You must be signed in to change notification settings - Fork 743
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
Corrupted segment reference count - corrupted index or hints #8535
Comments
So that traceback also happens AFTER BTW:
That is harmless.
But, obviously, that shouldn't happen.
|
Yes, this happens after
|
@ThomasWaldmann Can you think of any workaround/mitigation or would I be better off creating a new repo? |
Can you make a backup or snapshot of the repo and try just removing the hints file, running borg check --repair and then compact? |
Done. That seems to have worked, although the first check after deleting the hints was somewhat unhappy:
Thanks for your help! I still have the snapshot of the broken repo. If you'd like me to perform any forensics on that data, please let me know. |
Hmm, wondering why it complains about the index? You said you only deleted the hints? |
Correct. There was a hints and index with a matching suffix |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
BUG
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.4.0
Operating system (distribution) and version.
Ubuntu 24.04
Hardware / network configuration, and filesystems used.
How much data is handled by borg?
~ 3 TB
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg compact --info ssh://<user>@<user>.your-storagebox.de:23/./borg/antares
Describe the problem you're observing.
Hi there,
I guess this started when a nightly borg backup was interrupted by a scheduled hardware maintenance at our ISP. Long story short, compacting throws an error
Corrupted segment reference count - corrupted index or hints
(see full log below).I have already tried running
borg check --repair
as well as deleting the last few archives to no avail.This is the same machine and remote as in #6140, but the error seems to be different.
Any ideas?
Thanks,
Thilo
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: