Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Git problems on x86_64 Solaris 11

user12850720Dec 7 2017 — edited Feb 1 2018

We've a diverse set of platforms we develop on, including Solaris 10 and Solaris 11, x86 and SPARC.

This problem seems to be specific to solaris 11 x86 (we use 64-bit OS) as we have not witnessed this under SPARC or Solaris 10 x86.

Git appears to fail when cloning (and fetching) large amounts of data:

> git clone git@octocat/pdfl15_all

Initialized empty Git repository in /raid/proj/procyon/checkouts-procyon/robb/apdfl-test/pdfl15_all/.git/

remote: Counting objects: 145592, done.

remote: Compressing objects: 100% (44/44), done.

remote: Total 145592 (delta 16), reused 7 (delta 0), pack-reused 145548

Receiving objects: 100% (145592/145592), 910.39 MiB | 42.63 MiB/s, done.

error: inflate: data stream error (incorrect data check)

fatal: serious inflate inconsistency

fatal: index-pack failed

The failures happen with any repository, never on Solaris 10, and are somewhat intermittent.  I've also noticed that setting Git's debugging environment variables seems to reduce the probability.

(for example)

> GIT_TRACE=2 GIT_CURL_VERBOSE=2 GIT_TRACE_PERFORMANCE=2 GIT_TRACE_PACK_ACCESS=2 GIT_TRACE_PACKET=2 GIT_TRACE_PACKFILE=2 GIT_TRACE_SETUP=2 GIT_TRACE_SHALLOW=2 git clone git@octocat/pdfl15_all

I've also tried building my own git, version 1.9.5 and 2.15.0.106.g7bc7776.dirty which both fail the same way.

(master)$ PATH=/opt/git-1.9.5/bin:$PATH git fetch --all

Fetching origin

remote: Counting objects: 145592, done.

remote: Compressing objects: 100% (44/44), done.

error: inflate: data stream error (incorrect data check)03 MiB/s  

fatal: pack has bad object at offset 241467669: inflate returned -3

error: fetch died of signal 13

error: Could not fetch origin

Has anyone else seen or resolved this issue?

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 1 2018
Added on Dec 7 2017
1 comment
960 views