diff options
| author |  http://joey.kitenet.net/ <joey@web> | 2012-02-15 15:22:56 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-02-15 15:22:56 +0000 |
| commit | 623a42b0e922d08fd8672892508d7ac32f2d8225 (patch) | |
| tree | 2f04ba9c33a84a1baa2f79178f4643399eb02303 | |
| parent | 88b3ee89689ce874b48ce8eaa7586d02d06382ab (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/fsck_gives_false_positives/comment_5_86484a504c3bbcecd5876982b9c95688._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/fsck_gives_false_positives/comment_5_86484a504c3bbcecd5876982b9c95688._comment b/doc/forum/fsck_gives_false_positives/comment_5_86484a504c3bbcecd5876982b9c95688._comment new file mode 100644 index 000000000..7f0fbf96a --- /dev/null +++ b/doc/forum/fsck_gives_false_positives/comment_5_86484a504c3bbcecd5876982b9c95688._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joey.kitenet.net/" + nickname="joey" + subject="comment 5" + date="2012-02-15T15:22:56Z" + content=""" +The symlinks are in the git repository. So if the rsync damanged one, git would see the change. And nothing that happens to the symlinks can affect fsck. + +git-annex does not use hard links at all. + +fsck corrects mangled file permissions. It is possible to screw up the permissions so badly that it cannot see the files at all (ie, chmod 000 on a file under .git/annex/objects), but then fsck will complain and give up, not move the files to bad. +So I don't see how a botched rsync could result in fsck moving a file with correct content to bad. +"""]] |