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
Tree xxxxxx not found in repository and abort #1798
Comments
Thanks for the report, this needs to be handled better. Please be aware that it looks like a file is missing from the repository, this is unfortunately not the first time it was reported to happen with the OVH Swift backend. I'm not aware of anything we could do from restic's side of view here. |
I'm aware that it seems there are problems on OVH side. I opened this issue only for handle this error in a better way 😄 |
We've the same issue with s3:
Backup started with 0.8.0, we've seen this error with 0.8.1 and even after updating to 0.9.0 |
@rmoriz Can you try with version |
@fab120 Still having the issue wie |
I also have the same issue with a Backblaze B2 storage backend. How come that all these backends loose files? BTW the restic version for me was 0.9.1 |
Closing this as the issue is quite old and there have been several fixes which could be related to this issue. Contained in a released restic version: #2773 #2674 #1494 . To be released: #2842 Recovering from really missing trees is tracked via #1759. Please open a new issue if the problem persists with a recent restic version. |
Output of
restic version
restic 0.9.0 compiled with go1.10.2 on linux/amd64
How did you run restic exactly?
restic -r swift:backup:/ forget --group-by paths --keep-last 15 --prune
What backend/server/service did you use to store the repository?
OVH object storage
Expected behavior
Warn about the missing object and continue the execution.
Actual behavior
Steps to reproduce the behavior
Running
resting forget --prune
against a repoDid restic help you or made you happy in any way?
Restic is really awesome! Thanks for developing this!
The text was updated successfully, but these errors were encountered: