summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web>2011-10-29 21:36:06 +0000
committerGravatar admin <admin@branchable.com>2011-10-29 21:36:06 +0000
commita183487cd5477add59f470a42b18ec0c233bfb06 (patch)
treeab30e1c99550e0a4e3f2cddfda7672d81941d52b
parent36f63ab19e54f51561dd9f2946c68037a8e99791 (diff)
-rw-r--r--doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn b/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn
index 1f5667a11..fe6536b6a 100644
--- a/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn
+++ b/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn
@@ -42,3 +42,16 @@
>>>>>>> The "checksum" line is regarding **different** file than the
>>>>>>> not enough copies message. fsck does not attempt to checksum a file
>>>>>>> that is not present. [[done]] --[[Joey]]
+
+
+>>>>>>>> I realized early on that I pasted the wrong cross-passage, but as there is a ton of the same output, I didn't think it would matter. I wasn't aware that it does not try to checksum when there aren't enough copies. To be fair, you only just mentioned that.
+>>>>>>>> Personally, I think that's a bug as it makes ensuring local correctness before copying a file to remotes impossible.
+>>>>>>>> Either way, I really didn't know it actually _skipped_ checksumming; that part was missing.
+>>>>>>>> For the benefit of anyone else who might read this, this is the correct order:
+
+ fsck foo (fixing location log)
+ Only 1 of 2 trustworthy copies exist of foo
+ Back it up with git-annex copy.
+ (checksum...) failed
+
+>>>>>>>> If you would like to keep things this way, fine. I think it's less than ideal, but I don't want to argue, either. -- Richard