On Oct 26, 7:05 am, "Michael P. Soulier" <msoul...@digitaltorque.ca>
> On 24/10/10 Mike said:
> > This weekend we're cutting over to use git for our source code control
> > system. I've imported about 20 years worth of previous history using
> > "git cvsimport" (takes about four hours). I then cloned the resulting
> > repository onto five different machines (four Linux, one Solaris).
> > I've set up a cron job to do a nightly "git fsck" on each of the five
> > machines, and last night, two of the machines reported fsck errors on
> > their initial run. Here's a sample of the errors:
> If you compare to a good copy, is Git correct? If it is, then the files were
> corrupted somehow.
Thanks for your suggestion.
It turned out that an old libcrypto was to blame. The clone was
copying the repository to the pack-file with no errors, but the index
file that was created during the clone process was incorrect on the
two "bad" machines. These machines (Fedora Core 2 vintage) were
running openssl-0.9.7a-26 and openssl-0.9.7a-35, and upgrading solved
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at