Re: git-reflog 70 minutes at 100% cpu and counting

From: Nicolas Pitre <nico@fluxnic.net>
Date: Dec 18, 2009, 03:33 UTC
Message-ID: <alpine.LFD.2.00.0912172149020.23173@xanadu.home>
In-Reply-To: <1261067369.2868.10.camel@localhost>

On Thu, 17 Dec 2009, Eric Paris wrote:

Show 14 quoted lines

> This alone almost certainly tells me how I broke it.
> 
> For quite some time (a period of months) linux-next was broken and I had
> to carry a patch to ACPI to make it boot.  I dropped that patch at the
> head of my stgit trees in all of my repositories.  So I wouldn't be at
> all surprised to learn that eventually kernel-2 found that object in
> kernel-1.  Sometime when I dropped that patch from kernel-1 (because it
> finally got fixed upstream) I can see how it broke.
> 
> But now that patch shouldn't be needed by any tree since I have long
> since dropped it from the stgit stack.  So if we cleaned up all of the
> useless objects in this tree I bet this object wouldn't be needed.  Not
> exactly a situation that I'd expect git to be able to dig out of itself
> thought.

I let the script I provided previously ran for a while. And the commit I found to contain the missing object belongs to refs/patches/fsnotify/fsnotify-group-priorities.log. So I simply deleted that branch entirely and now the repack can proceed. And with a 'git gc --aggressive' the 1.2GB repository shrank to a mere 5.2 MB. :-) Of course I didn't bring back all the reflogs though. But I would have expected a repository reduction of the same magnitude even with them.

Nicolas