Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Retry blob loading if backend returns corrupted data #4440

Closed
MichaelEischer opened this issue Aug 6, 2023 · 1 comment
Closed

Retry blob loading if backend returns corrupted data #4440

MichaelEischer opened this issue Aug 6, 2023 · 1 comment
Labels
category: resilience preventing and recovering from repository problems type: feature enhancement improving existing features

Comments

@MichaelEischer
Copy link
Member

Output of restic version

0.16.0

What should restic do differently? Which functionality do you think we should add?

Repository.LoadBlob currently does not retry downloads which returned corrupted pack files. I guess we can add a retry there, similar to what’s already implemented for index files and similar.

Without such a retry, restic may run into problems with certain backends as in https://forum.restic.net/t/is-a-jottacloud-repo-reliable-seeking-user-input/6390/12 .

Follow-up to #3521
@MichaelEischer MichaelEischer added type: feature enhancement improving existing features category: resilience preventing and recovering from repository problems labels Aug 6, 2023
@MichaelEischer
Copy link
Member Author

Fixed by #4800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: resilience preventing and recovering from repository problems type: feature enhancement improving existing features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MichaelEischer