TheArchive/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-12-13 17:24:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

slightly polish changelogs

Browse Source
This commit is contained in:
Michael Eischer
2025-09-15 19:52:24 +02:00
parent 4940e330c0
commit 9ef8e13102
6 changed files with 23 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
changelog/unreleased/issue-5467
View File

@@ -1,8 +1,8 @@
Bugfix: Improve handling of download retries in `check` command
In very rare cases, the `check` command could unnecessarily report a
repository damage if the backend returns incomplete, corrupted data on
the first download try which is resolved by a download retry.
In very rare cases, the `check` command could unnecessarily report repository
damage if the backend returned incomplete, corrupted data on the first download
try which is afterwards resolved by a download retry.
This could result in an error output like the following:
```
@@ -13,15 +13,14 @@ check successful on second attempt, original error pack 34567890ab[...] contains
Fatal: repository contains errors
```
This fix only applies to a very specific case. The required condition is
a `operation successful after 1 retries` error in the log, later followed by
a `check successful on second attempt, original error` error that only reports
This fix only applies to a very specific case where the log shows
`operation successful after 1 retries` followed by a
`check successful on second attempt, original error` that only reports
`ciphertext verification failed` errors in the pack file. If any other errors
are reported in the pack file, then the repository still has to be considered
as damaged.
Now, only the check result of the last download retry is reported as
intended.
Now, only the check result of the last download retry is reported as intended.
https://github.com/restic/restic/issues/5467
https://github.com/restic/restic/pull/5495