2021-06-30 20:44:30 +00:00
|
|
|
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.
|
2021-06-30 21:20:15 +00:00
|
|
|
>
|
|
|
|
|
> Reproed on my own laptop, with the family annex. However,
|
|
|
|
|
> it is not fully repoducible, I repeated the same steps
|
|
|
|
|
> again and it didn't happen. Those were: Clone;
|
|
|
|
|
> git remote rm origin; git annex schedule here 'fsck self 30m every day at
|
|
|
|
|
> any time'; git annex assistant
|
|
|
|
|
>
|
|
|
|
|
> Hypothesis: Maybe fsck is failing due to some other change
|
|
|
|
|
> that is being made to the git repo at the same time it's running?
|
|
|
|
|
> I noticed some files being downloaded from the web at the same
|
|
|
|
|
> time the failed fsck was running.
|
