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
Possibility to run borg check for specific segment(s) #8070
Comments
Can you post the output of |
BTW, I can't explain how Ctrl-C would ever lead to that state (a missing, but referenced segment file) in a repository. So there might be some unidentified additional problem: "why does the repo lose files"? Maybe consider a |
Besides the stuff you already noted, there is only As there is known damage in your repo and we do not really know whether it is just that single segment file, it would be better to run a full check --repair (including the high level archives part). |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
Question
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
v1.2.0 (Ubuntu package)
and
v1.2.7 (fat binary for ARM on Synology)
Operating system (distribution) and version.
Ubuntu 22.04 on x64, and Synology OS on ARM.
Hardware / network configuration, and filesystems used.
ext4
How much data is handled by borg?
~400 GB
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg check, borg delete, borg create - doesn't matter
Describe the problem you're observing.
I canceled a running backup operation (using Ctrl-C), which was backing up to a SMB mount onto a Synology NAS.
After this action I was left with a checkpoint snapshot which apparently has missing archives:
borg check
on this archive would take over 8 hours (extrapolated) and was canceled twice because of network issues, so I'd like to avoid running it if possible. Deleting the broken snapshot would be OK, howeverborg delete ::linuxkiste-2024-01-29T20:13:27.checkpoint
throws the same exception, so I cannot even delete the snapshot which has this problem (not even with--force
).Would
borg check --repair
fix this error?If so, can I run
borg check
just for this single segment, and/or somehow force-delete the last checkpoint snapshot?I know I can use --max-duration, but this too starts at the beginning and (probably needlessly) scans >17000 512MB files.
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes, every time.
The text was updated successfully, but these errors were encountered: