diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-01-14 16:27:01 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-01-14 16:27:01 +0000 |
| commit | 6b9460eae3837b815657dff91206bc0c37905bee (patch) | |
| tree | 8dad20466508bf592fa74b26580cbb25ae0a9498 | |
| parent | 22c75fc57f6613ece366d1712d6a2aede5409bf7 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment new file mode 100644 index 000000000..543777e26 --- /dev/null +++ b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.7.238" + subject="comment 1" + date="2013-01-14T16:26:59Z" + content=""" +Why stop at checking twice? The second check could also fail with a read error, and perhaps the third one would succeed. :P + +Seriously, I doubt that this is likely to be a benefit with a modern drive. If the file has a read error once, then error correction has already failed, and it's likely to fail again. Even if it managed to succeed the second time, you have a file that is being read wrong some of the time, which is not a good thing for fsck to leave unnoticed. + +Fsck moves bad files to `.git/annex/bad`, so the data in them can be recovered if it comes to that. Hopefully +though, there's a copy of the file in another repository, so git-annex can just get it from there instead. +"""]] |