summaryrefslogtreecommitdiff
path: root/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn')
-rw-r--r--doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn3
1 files changed, 0 insertions, 3 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
deleted file mode 100644
index dba775d37..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-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]]