Re: git repack on shallow clone of large repo (linux kernel) hangs at "Enumerating objects"

From: Jeff King <peff@peff.net>
Date: May 17, 2021, 08:51 UTC
Message-ID: <YKIulliGp8hyf5Y6@coredump.intra.peff.net>
In-Reply-To: <c98e51b0-d89b-9170-e3bc-69ac9ec5e114@gmail.com>

On Sun, May 16, 2021 at 08:09:56PM +0700, Bagas Sanjaya wrote:

Show 29 quoted lines

> I have a shallow clone of linux-stable repo [1] on my computer. Now
> I'm trying to repack with `git repack -A -d`.
> 
> Before repacking, here is the object counts on my clone
> (`git count-objects -v`):
> 
> > count: 0
> > size: 0
> > in-pack: 3162206
> > packs: 17
> > size-pack: 3120393
> > prune-packable: 0
> > garbage: 0
> > size-garbage: 0
> 
> And I have 41496 commits (only on master).
> 
> And here are relevant config used:
> 
> > pack.deltacachesize=120M
> > pack.windowmemory=400M
> > pack.packsizelimit=650M
> > pack.autopacklimit=0
> 
> When I trigger repack operation, I expected that all objects on 17 packs
> are consolidated into several 650M-sized packs. However, in my case, repacking
> was hang at "Enumerating objects" stage, that is I stuck at:
> 
> "Eumerating objects: 902036"

You could try using strace or gdb to see what it's doing.

But as a guess, one thing that sometimes causes a stall near the end of "enumerating objects" is loosening unreachable objects that are currently packed. You told repack to use "-A", which asks to loosen those objects so they aren't lost when the old packs are deleted (as opposed to "-a").

You'd probably want to at least say "--unpack-unreachable=some.time" to avoid writing out ones which are not even recent (and which is what "git gc" will do under the hood).

But if you don't care about keeping them at all (e.g., because this is not an active repository where other simultaneous operations may be taking place, so you know it is safe to delete even recent ones), then just "git repack -a -d" is probably your best bet.

-Peff