From ab8ae254504ff9a1c6e744bca5f71dd695906a34 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 15 Jan 2013 16:16:15 -0400 Subject: [PATCH] close --- .../fsck_should_double-check_when_a_content-check_fails.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn b/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn index 07ac0407c8..dba775d37e 100644 --- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn +++ b/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn @@ -1 +1,3 @@ git annex fsck marks files as bad when the checksumming fails. But this could also be due to a read error when the actual data stored is correct. So, fsck should check twice when a checksum fails. + +> [[done]]; apparently problem was caused by bad RAM. --[[Joey]]