-
-
Notifications
You must be signed in to change notification settings - Fork 732
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 repo causes borg check, delete fail #1043
Comments
The repository is completely empty (no segments) that's where the "borg check" crash comes from. Other commands give me this error:
This error you show is interesting: |
Right. |
Yes, a check should be added that aborts earlier and with a more clear error message when a repository is opened that has no commits. |
can happen for not correctly initialized repos or corrupted repos. here: borg list failing more pretty
can happen for not correctly initialized repos or corrupted repos. here: borg list failing more pretty
better error handling for missing repo manifest, fixes #1043
I fixed this as good as possible:
|
I have this corrupted repo created with broked Fedora23 package on ppc64, where it segfaulted shortly after start.
Now both borg delete and borg check are really unhappy about this repo even after I did borg break-lock on it and removed the now stale lock.
I am attaching a sample. which is a tar inside of zip since github apparently does not support tar.gz files.
borg-repo.tar.zip
The errors I get are:
The text was updated successfully, but these errors were encountered: