diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawkHDm_DOFRcHYebCnnYKKyIwiPD4iOiiIU <Jrn@web> | 2013-01-13 14:13:59 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-01-13 14:13:59 +0000 |
| commit | 0ea118e150e1a776bf38f9feafbdedbf64d7c7fc (patch) | |
| tree | 740c2ff2fd2aa55298069369615ad5cf4600942e | |
| parent | 25dc0d97433958596cd2a400eb8a3561b6e610bd (diff) | |
| -rw-r--r-- | doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn | 1 |
1 files changed, 1 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 new file mode 100644 index 000000000..07ac0407c --- /dev/null +++ b/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn @@ -0,0 +1 @@ +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. |