git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>
Subject: Re: fetch and bundle don't work in (semi-)broken repo
Date: Tue, 19 Oct 2010 13:39:25 -0500	[thread overview]
Message-ID: <20101019183925.GF25139@burratino> (raw)
In-Reply-To: <20101019160957.GK11713@pengutronix.de>

Hi,

Uwe Kleine-König wrote:

> 	ukl@hostname:~/path1/linux-2.6$ git fetch ~/path2/linux-2.6 sectionmismatches
> 	remote: Counting objects: 118, done.
> 	remote: error: unable to find 40aaeb204dc04d3cf15c060133f65538b43b13b0
> 	remote: Compressing objects: 100% (83/83), done.
> 	remote: fatal: unable to read 40aaeb204dc04d3cf15c060133f65538b43b13b0
> 	error: git upload-pack: git-pack-objects died with error.
> 	fatal: git upload-pack: aborting due to possible repository corruption on the remote side.

Sounds like alternates or workdir allowed gc to be overzealous, indeed.

Could you:

 1. Make a copy of the corrupted repo, just in case.
 2. Explode all backs with "git unpack-objects"
 3. Identify the missing object, as explained in
    Documentation/howto/recover-corrupted-blob-object.txt?

With that information, it would be easier to examine whether and how
pack-objects could be smarter about fetching the non-missing objects.

> I don't know what 40aaeb204dc04d3cf15c060133f65538b43b13b0 is, but I
> think it's not necessary for the sectionmismatches branch:
> 
> 	ukl@hostname:~/path2/linux-2.6$ git format-patch linus/master..sectionmismatches
> 	0001-wip-enable-DEBUG_SECTION_MISMATCH.patch
[...]
> and linus/master is contained in ~/path1/linux-2.6, too.

Cc-ing Nico, pack-objects wizard.

Thanks for reporting.
Jonathan

  reply	other threads:[~2010-10-19 18:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 16:09 fetch and bundle don't work in (semi-)broken repo Uwe Kleine-König
2010-10-19 18:39 ` Jonathan Nieder [this message]
2010-10-19 20:11   ` Uwe Kleine-König
2010-10-19 20:48     ` Nicolas Pitre
2010-10-19 21:02       ` Jonathan Nieder
2010-10-20  3:06         ` Nicolas Pitre
2010-10-20  7:41           ` Uwe Kleine-König
2010-10-20 13:38             ` Nicolas Pitre
     [not found]               ` <20101020150810.GE19834@pengutronix.de>
     [not found]                 ` <alpine.LFD.2.00.1010201301130.2764@xanadu.home>
2010-10-21  7:11                   ` format-patch broken [Was: fetch and bundle don't work in (semi-)broken repo] Uwe Kleine-König
2010-10-21  8:12                     ` Uwe Kleine-König
2010-10-22  3:53                     ` Nicolas Pitre
2010-10-20  7:59       ` fetch and bundle don't work in (semi-)broken repo Uwe Kleine-König

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=20101019183925.GF25139@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).