From: Martin Fick <mfick@codeaurora.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Diagnosing stray/stale .keep files -- explore what is in a pack?
Date: Tue, 14 Jan 2014 12:36:44 -0700 [thread overview]
Message-ID: <201401141236.44393.mfick@codeaurora.org> (raw)
In-Reply-To: <CACPiFCJVx0dkkPQ=LosbAAKq7CvK6_yQL5QDHMYr5oJAS6wb6Q@mail.gmail.com>
Perhaps the receiving process is dying hard and leaving
stuff behind? Out-of-memory, out of disk space?
-Martin
On Tuesday, January 14, 2014 10:10:31 am Martin Langhoff
wrote:
> On Tue, Jan 14, 2014 at 9:54 AM, Martin Langhoff
>
> <martin.langhoff@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 <
> /var/lib/ppg/reports.git/objects/pack/pack-22748bcca7f50a
> 3a49aa4aed61444bf9c4ced685.idx
>
> 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).
>
> cheers,
>
>
> m
--
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-14 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 14:54 Diagnosing stray/stale .keep files -- explore what is in a pack? Martin Langhoff
2014-01-14 17:10 ` Martin Langhoff
2014-01-14 19:36 ` Martin Fick [this message]
2014-01-14 19:42 ` Martin Langhoff
2014-01-15 9:12 ` Jeff King
2014-01-15 13:42 ` Martin Langhoff
2014-01-15 17:49 ` Junio C Hamano
2014-01-15 23:50 ` Martin Langhoff
2014-01-16 1:14 ` Duy Nguyen
2014-01-21 5:19 ` Jeff King
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=201401141236.44393.mfick@codeaurora.org \
--to=mfick@codeaurora.org \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.