git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: srinivas naga vutukuri <srinivas.vutukuri@gmail.com>,
	git@vger.kernel.org
Subject: Re: git problem: pack has bad object at offset 77100841: inflate returned -3
Date: Tue, 12 Aug 2008 21:17:49 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0808122111180.9984@xanadu.home> (raw)
In-Reply-To: <20080806143310.GB28231@spearce.org>

On Wed, 6 Aug 2008, Shawn O. Pearce wrote:

> srinivas naga vutukuri <srinivas.vutukuri@gmail.com> wrote:
> > remote: Counting objects: 879862, done.
> > remote: Compressing objects: 100% (156686/156686), done.
> > fatal: pack has bad object at offset 77100841: inflate returned -3
> > fatal: index-pack failed
> > 
> > while doing "git clone" of linux kernel of latest 2.6.27-rc2.
> > But am able to do the latest stable successfully.
> ...
> > I am using cygwin, git 1.5.6.4
> 
> Where are you cloning from?
> 
> This is an indication that the data sent to your system from the
> remote side is corrupt.  Possibly a bad network link?
> 
> Remote side corruption should have been detected by the remote
> server as it was writing the data out.  The message above however
> came from your client, so the server seems to be OK.

Well, not exactly.  The server (git pack-objects) does skip some data 
integrity validation that the client (git index-pack) is doing anyway in 
order to cut cycles on the server machine.


Nicolas

      parent reply	other threads:[~2008-08-13  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  7:15 git problem: pack has bad object at offset 77100841: inflate returned -3 srinivas naga vutukuri
2008-08-06 14:33 ` Shawn O. Pearce
2008-08-06 15:04   ` srinivas naga vutukuri
2008-08-13  1:17   ` Nicolas Pitre [this message]

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.LFD.1.10.0808122111180.9984@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=srinivas.vutukuri@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 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).