TheArchive/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-12-11 18:47:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

extend changelog

Browse Source
This commit is contained in:
Michael Eischer
2025-09-08 11:54:29 +02:00
parent a5e814bd8d
commit 3a63430b07
1 changed files with 17 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
changelog/unreleased/issue-5467
View File

@@ -4,7 +4,23 @@ In very rare cases, the `check` command could unnecessarily report a
repository damage if the backend returns incomplete, corrupted data on repository damage if the backend returns incomplete, corrupted data on
the first download try which is resolved by a download retry. the first download try which is resolved by a download retry.
Now, only the check result of the last download attempt is reported as This could result in an error output like the following:
```
Load(<data/34567890ab>, 33918928, 0) returned error, retrying after 871.35598ms: readFull: unexpected EOF
Load(<data/34567890ab>, 33918928, 0) operation successful after 1 retries
check successful on second attempt, original error pack 34567890ab[...] contains 6 errors: [blob 12345678[...]: decrypting blob <data/12345678> from 34567890 failed: ciphertext verification failed ...]
[...]
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
`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. intended.
https://github.com/restic/restic/issues/5467 https://github.com/restic/restic/issues/5467