From: Denis Rosset <dr@racontemoi.ch>
To: git@vger.kernel.org
Subject: Git reproducible corruption errors on merge/checkout not detected by git fsck --full --strict
Date: Sun, 27 Dec 2009 22:59:04 +0100 [thread overview]
Message-ID: <501B634A-02B3-4F30-8E36-3AE76BA7A0D8@racontemoi.ch> (raw)
Hi all !
I use git regularly since twelve months; on one specific repository, I
had repetitive "inflate: data stream error (incorrect data check)"
errors. These errors appear when checking out from one branch to
another or when merging; however doing a "git fsck --full --strict" on
either the local repository or the remote repository before the
operation does not show anything wrong.
The bare repository is located on a Mac OS X 10.5 PPC server with Git
1.5.X.Y (X, Y not known), the local client is Git 1.6.6 installed
through MacPorts. I am stuck with Git 1.6.6 due to the MacPorts
architecture. Local zlib is 1.2.3_3.
I created a new local repository, reimported the files manually (only
the files, losing all the history in the process), and errors happen
again. The errors seems to appear when Git creates a local pack to
store the object files.
I am now installing Macports git 1.6.6 on the server to do further
testing.
My questions :
1) is "git fsck --full --strict" the most comprehensive check I can do
on a repository ?
2) are there known bugs leading to data corruption in the git 1.6.6
prerelease and/or zlib 1.2.3_3 ?
3) is there a verbose flag or a log I can consult (and eventually send
to this list) ?
Kind regards,
Denis Rosset
reply other threads:[~2009-12-27 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501B634A-02B3-4F30-8E36-3AE76BA7A0D8@racontemoi.ch \
--to=dr@racontemoi.ch \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).