Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: git@vger.kernel.org
Subject: Re: Problems getting rid of large files using git-filter-branch
Date: Wed, 7 Jan 2009 11:07:14 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0901071101480.7496@intel-tinevez-2-302> (raw)
In-Reply-To: <c09652430901061436w36c013ep938e9cfba43140c9@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 836 bytes --]

Hi,

On Tue, 6 Jan 2009, Øyvind Harboe wrote:

> On Tue, Jan 6, 2009 at 11:20 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>
> > $ git verify-pack -v $PACK | grep -v "^chain " | sort -n -k 4
> 
> I have never used the git verify-pack command, but I'm pretty sure the
> "Terminated" string isn't the normal output :-)
> 
> $ git verify-pack -v
> .git/objects/pack/pack-1e039b82d8ae53ef5ec3614a3021466663cc70a4
> Terminated

I did

	$ git grep Terminated

and came up empty :-)

Seriously, I guess this could be some OOM thing.  We _should_ handle this 
more gracefully, but it is possible that some uncatchable condition hits 
you, such as out-of-stack-space.

I'd try running the command either with strace or with gdb, and I'd look 
at $? after the command returns, to find out what is actually happening.

Hth,
Dscho

  reply	other threads:[~2009-01-07 10:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 21:59 Problems getting rid of large files using git-filter-branch Øyvind Harboe
2009-01-06 22:20 ` Johannes Schindelin
2009-01-06 22:36   ` Øyvind Harboe
2009-01-07 10:07     ` Johannes Schindelin [this message]
2009-01-07 10:15       ` Øyvind Harboe
2009-01-07 12:45         ` Johannes Schindelin
2009-01-07 18:18       ` Sitaram Chamarty
2009-01-06 22:31 ` Nicolas Pitre
2009-01-06 22:41   ` Øyvind Harboe
2009-01-06 23:17   ` Stephen R. van den Berg
2009-01-07  0:56     ` Nicolas Pitre
2009-01-07  8:26 ` Øyvind Harboe
2009-01-07 15:02   ` Nicolas Pitre

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=alpine.DEB.1.00.0901071101480.7496@intel-tinevez-2-302 \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=oyvind.harboe@zylin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox