From: Junio C Hamano <junkio@cox.net>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: Error converting from 1.4.4.1 to 1.5.0?
Date: Wed, 14 Feb 2007 09:45:14 -0800 [thread overview]
Message-ID: <7vy7n0pr9x.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <17875.17647.74882.218627@lisa.zopyra.com> (Bill Lear's message of "Wed, 14 Feb 2007 11:20:47 -0600")
Bill Lear <rael@zopyra.com> writes:
> % git fsck-objects --full
> error: Packfile .git/objects/pack/pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.pack SHA1 mismatch with itself
> fatal: failed to find delta-pack base object 90bad0d280a6d7c155bbd9582b35ffcf5e3bdd27
>
>
> % /usr/bin/git --version
> git version 1.4.4.1
>
> % /usr/bin/git fsck-objects --full
> error: Packfile .git/objects/pack/pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.pack SHA1 mismatch with itself
> fatal: failed to find delta-pack base object 90bad0d280a6d7c155bbd9582b35ffcf5e3bdd27
>
> So, all I did was try to do a commit with the new git ... haven't
> recloned, or pulled from upstream...
If you haven't packed the repository lately, the above indicates
this is not an issue between 1.4.4.1 and 1.5.0, but you had a
corrupt packfile before even started.
How big is this pack, what platform are you working on and whose
SHA-1 implementation do you use?
We used to have a bug that fed really large buffer to
SHA1_Update() function of the underlying SHA-1 library,
which was discovered exactly because somebody reported that
"mismatch with itself" message.
Also, do you have a huge blob in the repository? I do not know
if it is related but the write_sha1_file_prepare() function on
the codepath to write loose objects out would trigger the same
bug...
next prev parent reply other threads:[~2007-02-14 17:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 16:12 Error converting from 1.4.4.1 to 1.5.0? Bill Lear
2007-02-14 17:07 ` Bill Lear
2007-02-14 17:15 ` Junio C Hamano
2007-02-14 17:20 ` Bill Lear
2007-02-14 17:45 ` Junio C Hamano [this message]
2007-02-14 20:49 ` Bill Lear
2007-02-14 20:58 ` Bill Lear
2007-02-14 21:19 ` Linus Torvalds
2007-02-14 21:40 ` Bill Lear
2007-02-14 21:47 ` Junio C Hamano
2007-02-14 21:52 ` Junio C Hamano
2007-02-14 22:04 ` Johannes Schindelin
2007-02-14 22:13 ` Junio C Hamano
2007-02-14 22:32 ` Johannes Schindelin
2007-02-15 0:41 ` Jakub Narebski
2007-02-15 0:54 ` Olivier Galibert
2007-02-15 1:36 ` Johannes Schindelin
2007-02-14 22:02 ` Johannes Schindelin
2007-02-14 22:27 ` Nicolas Pitre
2007-02-14 22:41 ` Bill Lear
2007-02-15 1:18 ` OT: data destruction classics (was: Re: Error converting from 1.4.4.1 to 1.5.0?) Simon 'corecode' Schubert
2007-02-15 2:13 ` Shawn O. Pearce
2007-02-15 2:51 ` Linus Torvalds
2007-02-15 10:24 ` Johannes Schindelin
2007-02-15 13:13 ` Michael K. Edwards
2007-02-15 11:58 ` Bill Lear
2007-02-15 9:13 ` Andy Parkins
2007-02-15 14:30 ` Mark Wooding
2007-02-14 23:24 ` Error converting from 1.4.4.1 to 1.5.0? Linus Torvalds
2007-02-14 23:03 ` Linus Torvalds
2007-02-15 8:40 ` Uwe Kleine-König
2007-02-14 21:12 ` Junio C Hamano
2007-02-14 21:18 ` Bill Lear
2007-02-14 21:14 ` Nicolas Pitre
2007-02-14 21:32 ` Junio C Hamano
2007-02-14 18:19 ` Linus Torvalds
2007-02-14 18:42 ` Linus Torvalds
2007-02-14 21:13 ` Bill Lear
2007-02-14 21:35 ` Linus Torvalds
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=7vy7n0pr9x.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.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).