Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Re: "git fsck" hanging (v1.7.3.2)

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:49:52

Hi Leo,

Leo Razoumov wrote:
And then it sits there spinning CPU (99%) and nothing happening for
over a minute or so and then it proceeds to conclusion. The whole
thing takes about 2 minutes

~/git-1.7.3.2> time git fsck
git fsck  98.27s user 2.78s system 98% cpu 1:42.48 total

I previously compiled git-1.6.5.8 in exactly the same way on the same
system and had no problems of any kind.
"git fsck" was completing in seconds even for large repos.
You are right --- there was a significant change in fsck 1.6.6:

Notes on behaviour change [1]
-------------------------

 * In this release, "git fsck" defaults to "git fsck --full" and
   checks packfiles, and because of this it will take much longer to
   complete than before.  If you prefer a quicker check only on loose
   objects (the old default), you can say "git fsck --no-full".  This
   has been supported by 1.5.4 and newer versions of git, so it is
   safe to write it in your script even if you use slightly older git
   on some of your machines.

Hope that helps.

[1] Documentation/RelNotes/1.6.6.txt
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help