summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar antymat <antymat@web>2012-02-14 22:48:38 +0000
committerGravatar admin <admin@branchable.com>2012-02-14 22:48:38 +0000
commit586e937ad0e5eb0074fd188cce728bc92a1e4ef9 (patch)
tree98ff228569f753578550a67347459bfd967908b6
parent7371209d13b595c427ae250ac22384d527127bbb (diff)
Added a comment
-rw-r--r--doc/forum/fsck_gives_false_positives/comment_2_f51c53f3f6e6ee1ad463992657db5828._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/fsck_gives_false_positives/comment_2_f51c53f3f6e6ee1ad463992657db5828._comment b/doc/forum/fsck_gives_false_positives/comment_2_f51c53f3f6e6ee1ad463992657db5828._comment
new file mode 100644
index 000000000..1e0111e67
--- /dev/null
+++ b/doc/forum/fsck_gives_false_positives/comment_2_f51c53f3f6e6ee1ad463992657db5828._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="antymat"
+ ip="77.190.74.127"
+ subject="comment 2"
+ date="2012-02-14T22:48:37Z"
+ content="""
+Thanks, joey, but I still do not know, why the file that has been (and *is*) OK according to separate sha1 and sha256 checks, has been marked 'bad' by `fsck` and moved to `.git/annex/bad`. What could be a reason for that? Could have `rsync` caused it? I know too little about internal workings of `git-annex` to answer this question.
+
+But one thing I know for certain - the false positives should *not* happen, unless something *is* wrong with the file. Otherwise, if it is unreliable, if I have to check twice, it is useless. I might as well just keep checksums of all the files and do all checks by hand...
+"""]]