From: Eric Paris <eparis@redhat•com>
To: Nicolas Pitre <nico@fluxnic•net>
Cc: Jeff King <peff@peff•net>, git@vger•kernel.org
Subject: Re: git-reflog 70 minutes at 100% cpu and counting
Date: Thu, 17 Dec 2009 22:55:50 -0500 [thread overview]
Message-ID: <1261108550.2868.63.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.0912172149020.23173@xanadu.home>
On Thu, 2009-12-17 at 22:33 -0500, Nicolas Pitre wrote:
> On Thu, 17 Dec 2009, Eric Paris wrote:
>
> > 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.
At least when I thought it was in ACPI I could imagine what I had done
wrong. Now I'm not so sure.
In any case, I've redesigned with a clear alternative repo that I never
work in and a cron job to clean up garbage every night. So hopefully
noone will hear from me again.
Nicolas, thanks so much for hunting this down!
-Eric
> 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
prev parent reply other threads:[~2009-12-18 3:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 20:28 git-reflog 70 minutes at 100% cpu and counting Eric Paris
2009-12-14 20:41 ` Sverre Rabbelier
2009-12-14 21:11 ` Jeff King
2009-12-14 21:20 ` Eric Paris
2009-12-14 21:23 ` Jeff King
2009-12-14 21:56 ` Eric Paris
2009-12-14 22:03 ` Sverre Rabbelier
2009-12-15 0:29 ` Nicolas Pitre
2009-12-14 22:14 ` Jeff King
2009-12-15 0:26 ` Nicolas Pitre
2009-12-15 0:36 ` Junio C Hamano
2009-12-15 3:58 ` Nicolas Pitre
2009-12-15 2:11 ` Eric Paris
2009-12-15 3:44 ` Nicolas Pitre
2009-12-15 2:39 ` Jeff King
2009-12-15 3:50 ` Nicolas Pitre
2009-12-15 4:26 ` Eric Paris
2009-12-16 3:03 ` Nicolas Pitre
2009-12-16 3:31 ` Eric Paris
2009-12-16 13:41 ` Eric Paris
2009-12-16 21:06 ` Nicolas Pitre
2009-12-16 22:37 ` Eric Paris
2009-12-17 5:38 ` Nicolas Pitre
2009-12-17 16:29 ` Eric Paris
2009-12-18 3:33 ` Nicolas Pitre
2009-12-18 3:44 ` Steven Noonan
2009-12-18 3:52 ` Eric Paris
2009-12-18 3:57 ` Nicolas Pitre
2009-12-18 4:26 ` Steven Noonan
2009-12-18 3:55 ` Eric Paris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1261108550.2868.63.camel@localhost \
--to=eparis@redhat$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=nico@fluxnic$(echo .)net \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox