diff options
author | http://joey.kitenet.net/ <joey@web> | 2012-02-14 22:57:29 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2012-02-14 22:57:29 +0000 |
commit | e04e05ef1b4e4dbf738698d5365c8f0507e93465 (patch) | |
tree | 8fa2371170ca5113cf39229401e3320c90e08792 | |
parent | 586e937ad0e5eb0074fd188cce728bc92a1e4ef9 (diff) |
Added a comment
-rw-r--r-- | doc/forum/fsck_gives_false_positives/comment_3_692d6d4cd2f75a497e7d314041a768d2._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/fsck_gives_false_positives/comment_3_692d6d4cd2f75a497e7d314041a768d2._comment b/doc/forum/fsck_gives_false_positives/comment_3_692d6d4cd2f75a497e7d314041a768d2._comment new file mode 100644 index 000000000..bd807f404 --- /dev/null +++ b/doc/forum/fsck_gives_false_positives/comment_3_692d6d4cd2f75a497e7d314041a768d2._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joey.kitenet.net/" + nickname="joey" + subject="comment 3" + date="2012-02-14T22:57:29Z" + content=""" +All that git annex fsck does is checksum the file and move it away if the checksum fails. + +If bad data was somehow read from the disk that one time, what you describe could occur. I cannot think of any other way it could happen. +"""]] |