Re: Git hangs at “Writing objects: 11%”

[Jeff King <peff@peff.net>]

On Thu, May 24, 2012 at 05:40:41PM -0400, Timothy Normand Miller wrote:

> I've run into a problem that I cannot debug.  I've talked with people
> at length on IRC, I've made ample use of Google.  I'm getting nowhere.
> I'm not even getting any attention on stackexchange (where usually,
> questions are answered with surprising alacrity).  
> 
> This is not the common scenario of Windows and git-daemon that I have
> seen answered elsewhere. This is Linux to Linux, using ssh. On both
> the client and server, git version is 1.7.8.6.

I'd first start with trying to remove as many variables as possible.
Does the problem only happen over ssh, or does it also happen when
pushing across a pipe to a repo on the local machine? If so, does it
also happen during a fetch of the same data?

If you can reproduce it at will (which it sounds like you can), you
could also try some older or newer git versions to see if they work any
better. If you can find a working version, it might be worth trying to
bisect and find the commit that introduces the breakage.

If the problem still exists in the latest version, then I'd start by
stracing as much as possible. On the client side, you can use "strace
-f" to see what all of the processes are doing; you'll probably also
want to pass:

  --receive-pack='strace -f -o foo.out git-receive-pack'

to git-push to ask the remote side to strace. There's a reasonable
chance you'll simply see that the client side is waiting on the server
side for I/O, so you'll want to know what the server side is doing.

I see you posted an strace snippet of a process waiting in select() on
stack overflow. It's hard to tell what's going on from there, though,
because we can't see which processes are which (we see the pids, but we
don't know which programs they're running, or where the commands go). A
full strace log would help a lot (if it's long and you need a place to
post it, try something like https://gist.github.com).

And finally, if the repo is something you can make public, I can try to
reproduce on my machine. That might tell us if the problem is with your
repo, or something else about your machines or setup.

-Peff