git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yossi Leybovich" <sleybo@gmail.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
Cc: "Andreas Ericsson" <ae@op5.se>,
	git@vger.kernel.org, "Yossi Leybovich" <sleybo@mellanox.co.il>
Subject: Re: corrupt object on git-gc
Date: Fri, 9 Nov 2007 10:53:46 -0500	[thread overview]
Message-ID: <4fe79b4b0711090753r52abd3e1ree64271c0fa229f6@mail.gmail.com> (raw)
In-Reply-To: <47347E0E.1040205@viscovery.net>

On Nov 9, 2007 10:34 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Yossi Leybovich schrieb:
> > [about corrupt loose object '4b9458b3786228369c63936db65827de3cc06200']
>
> You can try to create a clone (after you have fixed up the artificial
> breakages that you made). If that goes well, then the bad object is
> referenced only from reflogs.
>


git clone ib ib-clone
Initialized empty Git repository in /home/mellanox/work/symm/ib-clone/.git/
0 blocks



[mellanox@mellanox-compile ib-clone]$  cd ib-clone/

[mellanox@mellanox-compile ib-clone]$ git branch -a
* mlx4
  origin/HEAD
  origin/master
  origin/mlx4
  origin/mlx4-work
  origin/mthca
  origin/second_port


[mellanox@mellanox-compile ib-clone]$ git-gc
Generating pack...
Done counting 3288 objects.
Deltifying 3288 objects...
error: corrupt loose object '4b9458b3786228369c63936db65827de3cc06200'
fatal: object 4b9458b3786228369c63936db65827de3cc06200 cannot be read
error: failed to run repack


So still I cant pack my repository


> -- Hannes
>
>

  reply	other threads:[~2007-11-09 15:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 13:38 corrupt object on git-gc Yossi Leybovich
2007-11-09 13:46 ` Andreas Ericsson
2007-11-09 15:01   ` Yossi Leybovich
2007-11-09 15:34     ` Johannes Sixt
2007-11-09 15:53       ` Yossi Leybovich [this message]
2007-11-09 16:03         ` Johannes Sixt
2007-11-09 16:03         ` Nicolas Pitre
2007-11-09 16:31           ` Yossi Leybovich
2007-11-09 16:52             ` Nicolas Pitre
2007-11-09 16:28 ` Linus Torvalds
2007-11-09 17:28   ` [PATCH] add a howto document about corrupted blob recovery Nicolas Pitre
2007-11-09 17:30     ` Johannes Schindelin
2007-11-26  2:12     ` J. Bruce Fields
2007-11-09 17:53   ` corrupt object on git-gc Yossi Leybovich
2007-11-09 18:02     ` Linus Torvalds
2007-11-09 18:37       ` Yossi Leybovich
2007-11-09 18:55         ` Linus Torvalds
2007-11-09 19:07           ` Mike Hommey
2007-11-09 19:41             ` Yossi Leybovich
2007-11-09 19:52               ` Mike Hommey
     [not found] <6C2C79E72C305246B504CBA17B5500C902535D9C@mtlexch01.mtl.com>
     [not found] ` <458BC6B0F287034F92FE78908BD01CE814472B3D@mtlexch01.mtl.com>
2007-11-08 23:59   ` Yossi Leybovich
2007-11-09  5:13     ` Christian Couder
2007-11-09 12:16       ` Yossi Leybovich
2007-11-09 17:45         ` Junio C Hamano
2007-11-09  8:10     ` Alex Riesen
2007-11-09 12:23       ` Yossi Leybovich
2007-11-09 12:56         ` Andreas Ericsson
2007-11-09 16:17       ` 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=4fe79b4b0711090753r52abd3e1ree64271c0fa229f6@mail.gmail.com \
    --to=sleybo@gmail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=sleybo@mellanox.co.il \
    /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;
as well as URLs for NNTP newsgroup(s).