summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn2
1 files changed, 2 insertions, 0 deletions
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 07ac0407c..dba775d37 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]]