From 0ffcfbdca659be8977f2a74386c9c7a06f067acb Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 30 Jun 2021 16:44:30 -0400 Subject: [PATCH] bug --- doc/bugs/Git_repos_corrupt_themselves.mdwn | 3 ++- doc/bugs/assistant_repair_misfires.mdwn | 15 +++++++++++++++ 2 files changed, 17 insertions(+), 1 deletion(-) create mode 100644 doc/bugs/assistant_repair_misfires.mdwn diff --git a/doc/bugs/Git_repos_corrupt_themselves.mdwn b/doc/bugs/Git_repos_corrupt_themselves.mdwn index 9964c48545..9bef074686 100644 --- a/doc/bugs/Git_repos_corrupt_themselves.mdwn +++ b/doc/bugs/Git_repos_corrupt_themselves.mdwn @@ -105,4 +105,5 @@ Git fsck spat out a huge list of broken blobs and trees. There are a surprising amount of weird bugs and quirks like these but it's such an amazing tool, there's nothing like it. -> [[fixed|done]] --[[Joey]] +> [[fixed|done]] although I have opened [[assistant_repair_misfires]] for +> part of the cause of this. --[[Joey]] diff --git a/doc/bugs/assistant_repair_misfires.mdwn b/doc/bugs/assistant_repair_misfires.mdwn new file mode 100644 index 0000000000..fbb6a8effb --- /dev/null +++ b/doc/bugs/assistant_repair_misfires.mdwn @@ -0,0 +1,15 @@ +The assistant's git-annex repair sometimes happens when git fsck does not +actually detect any problems. + +See [[Git_repos_corrupt_themselves]] of which this was part of the cause, +although the data loss part of that was solved. + +I saw this happen on my sister's laptop, in a freshly cloned repo, +with a git-annex version that fixed that data loss. +assistant was set up to fsck and on the very first fsck it started git +repair. git fsck reported no problems at all. --[[Joey]] + +> .git/annex/fsckresults/$uuid was empty, which means that +> writeFsckResults was called with FsckFailed. So apparently +> the fsck exited nonzero for some reason, but did not detect +> any misssing shas.