git problem: pack has bad object at offset 77100841: inflate returned -3

git problem: pack has bad object at offset 77100841: inflate returned -3

[srinivas naga vutukuri]

I am facing the error

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.

Could you help me out in get rid off the problem. And am new to git usage,
so correct me if am doing any wrong.

I am using cygwin, git 1.5.6.4


best regards,
srinivas.

Re: git problem: pack has bad object at offset 77100841: inflate returned -3

[Shawn O. Pearce]

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.

-- 
Shawn.

Re: git problem: pack has bad object at offset 77100841: inflate returned -3

[srinivas naga vutukuri]

Hi,

On Wed, Aug 6, 2008 at 8:03 PM, Shawn O. Pearce <spearce@spearce.org> 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.
>
> --
> Shawn.
>
I am gone to the site: http://www.kernel.org

from this place
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=summary

trying out, for 2.6.27-rc2
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

which is causing the problem,

But, from the place,
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fstable%2Flinux-2.6.26.y.git;a=summary
trying for stable.
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.26.y.git
is working fine...

Could any possible clue from this...

best regards,
srinivas.

Re: git problem: pack has bad object at offset 77100841: inflate returned -3

[Nicolas Pitre]

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