From: Thomas Glanzmann <thomas@glanzmann.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nicolas Pitre <nico@cam.org>, GIT <git@vger.kernel.org>,
Michael Gernoth <simigern@cip.informatik.uni-erlangen.de>
Subject: Re: fatal: serious inflate inconsistency
Date: Fri, 8 Jun 2007 20:24:12 +0200 [thread overview]
Message-ID: <20070608182412.GQ2335@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <alpine.LFD.0.98.0706080959570.4205@woody.linux-foundation.org>
Hello Linus,
> Could you compile your own git? If so, please try this patch on top of
> current git, to make the error message a bit more informative.
(tomcat-05) [/usr/src] scp 131.188.30.102:/var/tmp/sithglan/git-core-1.5.2.1/../git-core_1.5.2.1-1_i386.deb .
Warning: Permanently added '131.188.30.102' (RSA) to the list of known hosts.
git-core_1.5.2.1-1_i386.deb 100% 3511KB 1.7MB/s 00:02
(tomcat-05) [/usr/src] / dpkg -i git-core_1.5.2.1-1_i386.deb
(Reading database ... 13273 files and directories currently installed.)
Preparing to replace git-core 1:1.5.2.1-1 (using git-core_1.5.2.1-1_i386.deb) ...
Unpacking replacement git-core ...
Setting up git-core (1.5.2.1-1) ...
(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: -3 (invalid distance too far back)
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.
I talked to Michael and he is certain that the machine has a memory
corruption the next thing I am going to do is compiling a kernel in an
endless loop. Again if somone needs shell access just send me your ssh
key.
The complete build log is on (well not the complete log the first line is
missing because my screen backlog has _only_ 10000 lines (a memory issue)):
The first line is:
wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1-1.dsc
The rest is here:
http://wwwcip.informatik.uni-erlangen.de/~sithglan/screen-exchange.bz2 (32k)
Thanks,
Thomas
next prev parent reply other threads:[~2007-06-08 18:24 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
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 [this message]
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=20070608182412.GQ2335@cip.informatik.uni-erlangen.de \
--to=thomas@glanzmann.de \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=simigern@cip.informatik.uni-erlangen.de \
--cc=torvalds@linux-foundation.org \
/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).