git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Thomas Glanzmann <thomas@glanzmann.de>
Cc: GIT <git@vger.kernel.org>
Subject: Re: fatal: serious inflate inconsistency
Date: Fri, 08 Jun 2007 09:48:42 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.0.99.0706080931330.12885@xanadu.home> (raw)
In-Reply-To: <20070608110536.GD2335@cip.informatik.uni-erlangen.de>

On Fri, 8 Jun 2007, Thomas Glanzmann wrote:

> Hello,
> and here is another one I guess: ;-(
> 
>         (tomcat-05) [/usr/src] git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>         Initialized empty Git repository in /usr/src/linux-2.6/.git/
>         remote: Generating pack...
>         remote: Done counting 496911 objects.
>         remote: Deltifying 496911 objects...
>         remote:  100% (496911/496911) done
>         Indexing 496911 objects...
>         remote: Total 496911 (delta 401539), reused 493712 (delta 398653)
>         100% (496911/496911) done
>         Resolving 401539 deltas...
>         fatal: serious inflate inconsistency
>         fatal: index-pack died with error code 128
>         fetch-pack from
>         'git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git' failed.
>         (tomcat-05) [/usr/src] git version
>         git version 1.5.2.1

This is bad.

index-pack works like this:

1) it receives data over the network:
   1a) it writes a copy of that data to disk to create a pack
   1b) it deflates that data in parallel to compute its SHA1

2) when done, it resolves deltas and to do so:
   2a) it deflates the base object data from 1a
   2b) it applies the delta over the base object data then compute its 
       SHA1

In your case it seems that 1B and 2A don't produce the same deflated 
data somehow.

Is it reproducible?
Are you using Linux?  What kernel version?
Are you using NFS?

If it isn't reproducible then you might possibly have been the victim of 
faulty hardware.


Nicolas

  reply	other threads:[~2007-06-08 13:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 11:05 fatal: serious inflate inconsistency Thomas Glanzmann
2007-06-08 13:48 ` Nicolas Pitre [this message]
2007-06-08 13:50   ` Thomas Glanzmann
2007-06-08 15:37     ` Thomas Glanzmann
2007-06-08 15:39       ` Thomas Glanzmann
2007-06-08 16:15       ` Nicolas Pitre
2007-06-08 17:01       ` Linus Torvalds
2007-06-08 18:24         ` Thomas Glanzmann
2007-06-08 18:52           ` Linus Torvalds
2007-06-08 19:06             ` Linus Torvalds
2007-06-08 19:33               ` Thomas Glanzmann
2007-06-08 20:45                 ` Marco Roeland
2007-06-09  0:13                   ` Thomas Glanzmann
2007-06-09 21:12                     ` Thomas Glanzmann
2007-06-10  0:30                       ` Linus Torvalds
2007-06-10  0:50                 ` Martin Langhoff
2007-06-17  8:01 ` Thomas Glanzmann
  -- strict thread matches above, loose matches on Subject: below --
2007-11-09 14:14 bob
2007-11-09 16:11 ` Nicolas Pitre
2007-11-09 18:06   ` bob

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.0.99.0706080931330.12885@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=thomas@glanzmann.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).