mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2013-01-14 16:27:01 +00:00 • committed by admin
parent 3f159aae99
commit 41e1a9b6bc
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment Normal file
View file

@ -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.
"""]]