Perhaps the receiving process is dying hard and leaving
stuff behind? Out-of-memory, out of disk space?
On Tuesday, January 14, 2014 10:10:31 am Martin Langhoff
> On Tue, Jan 14, 2014 at 9:54 AM, Martin Langhoff
> <martin.langh...@gmail.com> wrote:
> > Is there a handy way to list the blobs in a pack, so I
> > can feed them to git-cat-file and see what's in there?
> > I'm sure that'll help me narrow down on the issue.
> git show-index <
> cut -d\ -f2 | xargs -iHASH git --git-dir
> /var/lib/ppg/reports.git/ unpack-file HASH
> After a bit of looking at the output, clearly I have two
> clients, out of the many that connect here, that have
> the problem. I will be looking into those clients to see
> what's the problem.
> In my use case, clients push to their own head. Looking
> at refs/heads shows that there are stale .lock files
> there. Hmmm.
> This is on git 1.7.1 (RHEL and CentOS clients).
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html