bug
This commit is contained in:
parent
ada61676ff
commit
0ffcfbdca6
2 changed files with 17 additions and 1 deletions
|
@ -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]]
|
||||
|
|
15
doc/bugs/assistant_repair_misfires.mdwn
Normal file
15
doc/bugs/assistant_repair_misfires.mdwn
Normal file
|
@ -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.
|
Loading…
Add table
Add a link
Reference in a new issue