mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2020-05-04 13:25:10 -04:00
parent 3e91461c0f
commit 2ab2b1f9e2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/forum/Repair_in_steps__63__/comment_1_6a512ab2d6ea583a1913c9837e953760._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-05-04T17:07:55Z"
content="""
The command uses `git fsck` to get a list of git objects that are missing
from the repository. It then tries to get those objects from remotes. So,
skipping the fsck is not really possible.
Also in some cases, it may need to fsck again after the initial pass.
You must have an exceptionally large git repo (and/or slow computer) for git
fsck to take more than several minutes.
I wonder if passing --connectivity-only to git fsck speeds it up
significantly for you? Actually corrupted blobs are probably much rarer
than blobs that are just missing, so it might be that git annex repair
could optionally use that to run fsck faster.
"""]]