From: "Vanak, Ibrahim" <ibrahim.vanak@hpe.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: GIT issue while cloning (fatal: pack is corrupted (SHA1 mismatch)) !!!
Date: Tue, 28 May 2019 09:10:12 +0000 [thread overview]
Message-ID: <TU4PR8401MB121664A8A588D799803F1E84E11E0@TU4PR8401MB1216.NAMPRD84.PROD.OUTLOOK.COM> (raw)
Hello,
We are seeing issue with GIT 2.14 version. When we try to clone the repos, it is taking HUGE amount of time on HPUX, whereas on the linux machine with same network configuration, it's getting cloned in less than mins. So we want to know has anyone reported this issue? What is the fix for this? Has the fix been released for this? Whom should we contact for this?
Thanks & Regards,
Ibrahim Vanak
Below is the HPUX system where we are seeing issue, it is taking 1 hr 45 mins and later it failed:
root@sstl002.in.rdlabs.hpecorp.net# uname -a
HP-UX sstl002 B.11.31 U ia64 0158936019 unlimited-user license
root@sstl002.in.rdlabs.hpecorp.net# time git clone git@github.hpe.com:HPUX/SysFaultMgmt.git
Cloning into 'SysFaultMgmt'...
remote: Enumerating objects: 63627, done.
remote: Total 63627 (delta 0), reused 0 (delta 0), pack-reused 63627
Receiving objects: 100% (63627/63627), 681.90 MiB | 111.00 KiB/s, done.
fatal: pack is corrupted (SHA1 mismatch)
fatal: index-pack failed
real 104m3.373s
user 0m36.220s
sys 0m6.090s
You have mail in /var/mail/root
root@sstl002.in.rdlabs.hpecorp.net#
Below is the system where it has passed in less than 3 mins:
[root@chandana ~]# uname -a
Linux chandana.in.rdlabs.hpecorp.net 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@chandana ~]# time git clone git@github.hpe.com:HPUX/SysFaultMgmt.git
Cloning into 'SysFaultMgmt'...
remote: Enumerating objects: 63627, done.
remote: Total 63627 (delta 0), reused 0 (delta 0), pack-reused 63627
Receiving objects: 100% (63627/63627), 681.90 MiB | 5.59 MiB/s, done.
Resolving deltas: 100% (35495/35495), done.
Checking connectivity... done.
Checking out files: 100% (10634/10634), done.
real 2m46.517s
user 0m36.601s
sys 0m10.503s
next reply other threads:[~2019-05-28 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 9:10 Vanak, Ibrahim [this message]
2019-05-28 9:37 ` GIT issue while cloning (fatal: pack is corrupted (SHA1 mismatch)) !!! Jeff King
2019-05-28 9:51 ` Ævar Arnfjörð Bjarmason
2019-05-28 18:45 ` Vanak, Ibrahim
2019-05-28 21:30 ` Jeff King
2019-05-29 5:29 ` Vanak, Ibrahim
2019-05-29 9:06 ` Vanak, Ibrahim
2019-05-30 11:57 ` Jeff King
2019-06-11 16:39 ` Vanak, Ibrahim
2019-06-18 14:31 ` Vanak, Ibrahim
2019-06-18 17:15 ` Jeff Hostetler
2019-06-28 16:18 ` Vanak, Ibrahim
2019-06-28 23:55 ` Jeff King
2019-05-28 10:16 ` Johannes Schindelin
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=TU4PR8401MB121664A8A588D799803F1E84E11E0@TU4PR8401MB1216.NAMPRD84.PROD.OUTLOOK.COM \
--to=ibrahim.vanak@hpe.com \
--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).