From 3a63430b073ccebff28794b104d87390e9e39428 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Mon, 8 Sep 2025 11:54:29 +0200 Subject: [PATCH] extend changelog --- changelog/unreleased/issue-5467 | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/changelog/unreleased/issue-5467 b/changelog/unreleased/issue-5467 index f6dbd9309..4b50fc857 100644 --- a/changelog/unreleased/issue-5467 +++ b/changelog/unreleased/issue-5467 @@ -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 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(, 33918928, 0) returned error, retrying after 871.35598ms: readFull: unexpected EOF +Load(, 33918928, 0) operation successful after 1 retries +check successful on second attempt, original error pack 34567890ab[...] contains 6 errors: [blob 12345678[...]: decrypting blob 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. https://github.com/restic/restic/issues/5467