git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: GIT issue while cloning (fatal: pack is corrupted (SHA1 mismatch)) !!!

From
VIVanak, Ibrahim <ibrahim.vanak@hpe.com>
Date
Jun 11, 2019, 16:39 UTC
Message-ID
<TU4PR8401MB12163C00148C39F0083C732DE1ED0@TU4PR8401MB1216.NAMPRD84.PROD.OUTLOOK.COM>
In-Reply-To
<20190530115742.GC31607@sigill.intra.peff.net>
Thank Peff. Unfortunately I am living with this issue, no one able to find out what is causing this significant delay. Re-initiating this thread if someone can help on this.

Thanks & Regards, Ibrahim Vanak

-----Original Message-----
From: Jeff King [mailto:peff@peff.net] 
Sent: Thursday, May 30, 2019 5:28 PM
To: Vanak, Ibrahim <ibrahim.vanak@hpe.com>
Cc: git@vger.kernel.org
Subject: Re: GIT issue while cloning (fatal: pack is corrupted (SHA1 mismatch)) !!!
On Wed, May 29, 2019 at 09:06:18AM +0000, Vanak, Ibrahim wrote:
> After cloning when I tried to checkout a branch on HPUX and Linux, I 
> still significant time difference there as well even though network is 
> not involve here. Do you suspect anything with HPUX OS? Do you have 
> any mechanism to find out who is the causing gigantic delay ?
If it's happening for just a local checkout operation, I'd suspect very poor filesystem performance. On Linux, I'd run it under "perf" to see where the time is going. Or possibly "strace -T" to time system calls. I don't know what tools are available under HP-UX for that kind of profiling.
-Peff
Previous: Jeff KingNext: Vanak, Ibrahim
Message 9 of 14 in “GIT issue while cloning (fatal: pack is corrupted (SHA1 mismatch)) !!!”
  1. Vanak, IbrahimMay 28, 2019
  2. Jeff KingMay 28, 2019
  3. Ævar Arnfjörð BjarmasonMay 28, 2019
  4. Vanak, IbrahimMay 28, 2019
  5. Jeff KingMay 28, 2019
  6. Vanak, IbrahimMay 29, 2019
  7. Vanak, IbrahimMay 29, 2019
  8. Jeff KingMay 30, 2019
  9. Vanak, IbrahimJun 11, 2019
  10. Vanak, IbrahimJun 18, 2019
  11. Jeff HostetlerJun 18, 2019
  12. Vanak, IbrahimJun 28, 2019
  13. Jeff KingJun 28, 2019
  14. Johannes SchindelinMay 28, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.