From: Joey Hess Date: Mon, 12 Oct 2020 19:10:57 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~106^2~98 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=8e7eeb753df51e7ec2d81892d72b82ef4493009f;p=git-annex.git comment --- diff --git a/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_4_cbc49405ab99e8722216739732ce394d._comment b/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_4_cbc49405ab99e8722216739732ce394d._comment new file mode 100644 index 0000000000..2830733430 --- /dev/null +++ b/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_4_cbc49405ab99e8722216739732ce394d._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2020-10-12T19:04:49Z" + content=""" +This is not the kind of problem that `git-annex repair` can fix. +The problems it fixes are all where one clone of a repo has gotten some +object files corrupted by eg disk problems, but other clones still have +good copies of those object files. + +The reason `git-annex repair` reports it failed is because it sees that +`git fsck` is reporting a problem and the things it's tried to do didn't +fix it. + +Are the "missing files" missing in that their annexed content is not +present, or missing in that there is no annex symlink at all? In the former +case, you need `git annex fsck` on those files, or `git-annex get`. In the +latter case, if `git status` doesn't show a missing file as deleted, that +would be a very strange problem with git. +"""]]