summaryrefslogtreecommitdiff
path: root/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn
blob: dba775d37e5c4339fa30f6fc73b121f018ee8c00 (plain)
1
2
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]]