diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-01-15 16:16:15 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-01-15 16:16:15 -0400 |
| commit | 93607362fbb32d9804f61207678a2279ed059424 (patch) | |
| tree | d1495e70cad978575fca2e47edcdcb0fe195d2c6 | |
| parent | 860609e9525e0304202237cfe23ac9888c771545 (diff) | |
close
| -rw-r--r-- | doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn | 2 |
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]] |