diff options
author | Joey Hess <joeyh@joeyh.name> | 2016-10-31 14:00:37 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2016-10-31 14:00:37 -0400 |
commit | 82d567a73c5d688c3e0de0abb6005d1be1fa2668 (patch) | |
tree | e09fde43ba20f45e9a1595c53bff637cc968b293 /doc/bugs/git-annex_wants_to_repair_because_of_duplicateEntries_in_git_fsck | |
parent | 8da030d180fd749103e865626e2f5389729af3f8 (diff) |
Assistant, repair: Fix ignoring of git fsck errors due to duplicate file entries in tree objects.
Diffstat (limited to 'doc/bugs/git-annex_wants_to_repair_because_of_duplicateEntries_in_git_fsck')
-rw-r--r-- | doc/bugs/git-annex_wants_to_repair_because_of_duplicateEntries_in_git_fsck/comment_1_4cd4f4b5c34b3e1bf2989d0cc412ca4f._comment | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_wants_to_repair_because_of_duplicateEntries_in_git_fsck/comment_1_4cd4f4b5c34b3e1bf2989d0cc412ca4f._comment b/doc/bugs/git-annex_wants_to_repair_because_of_duplicateEntries_in_git_fsck/comment_1_4cd4f4b5c34b3e1bf2989d0cc412ca4f._comment new file mode 100644 index 000000000..ddda442e0 --- /dev/null +++ b/doc/bugs/git-annex_wants_to_repair_because_of_duplicateEntries_in_git_fsck/comment_1_4cd4f4b5c34b3e1bf2989d0cc412ca4f._comment @@ -0,0 +1,34 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-10-31T17:07:43Z" + content=""" +This was supposed to be dealt with in version 6.20161027. But, I see now +that the parser I thought was triggering on those missing object lines, +was not really (`extractSha` does not match in this case because of the +colon after the sha). + +Instead, the problem seems to be that `git fsck` is exiting nonzero. So it +assumes that fsck is failing without printing out any shas, which is a +condition that calls for repairs. + +About all I can think to do is, if fsck outputs "duplicateEntries" and +no other lines at all, and exits nonzero, treat this as a success. +This risks ignoring other reasons fsck might exit nonzero, but hopefully +it would output something else in such a case. I've implemented this. + +--- + +I am interested in getting at the root cause of the problem of +duplicate directory entries. It seems pretty likely to result from using +adjusted branches. + +It would be useful to get more information about the trees that fsck +is warning about; are they part of existing or past adjusted branches +or not? Are they merge commits? + +(Previously: [[forum/how_to_disaster_recovery]]) + +Leaving this bug open since we really need to get at the root cause of +the problem. +"""]] |