From 2e2d9cb2583d1d52809c3d0de66473787af240b0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 9 Jun 2015 15:41:16 -0400 Subject: [PATCH] followup --- ..._656986cdc4831a8d2f80432acaf8a884._comment | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_2_656986cdc4831a8d2f80432acaf8a884._comment diff --git a/doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_2_656986cdc4831a8d2f80432acaf8a884._comment b/doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_2_656986cdc4831a8d2f80432acaf8a884._comment new file mode 100644 index 0000000000..4346bebee9 --- /dev/null +++ b/doc/bugs/Corrupted_.git__47__annex__47__index_when_running_assistant/comment_2_656986cdc4831a8d2f80432acaf8a884._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-06-09T19:34:57Z" + content=""" +So, thanks for providing me the index file, but the relevant problem +seems to be that your index file refers to a git object that failed to make +it to disk. + +The most likely cause of this would be a crash before disk buffers got +flushed, or something like that. + +It's perfectly fine to remove your .git/annex/index if this happens. You +must have lost some information that was being committed to the git-annex +branch, so you might want to run `git annex fsck` to make sure everything +gets updated. + +I'd expect `git-annex repair` to detect this problem (and fix it the same +way you did). + +It's possible that the assistant's code for detecting when there are +problems doesn't work well enough for it to have +automatically detected and fixed this problem. Which is why I'm leaving +this bug open for now. +"""]]