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

Large pack causes git clone failures ... what to do?

From
Geoff Russell <geoffrey.russell@gmail.com>
Date
Aug 31, 2010, 07:16 UTC
Message-ID
<AANLkTi=1iLx=-9gxkGzuhrbpA005VPSp0itkAkOG4D4z@mail.gmail.com>
Hi,

I did a "git gc" on a repository and ended up with a 4GB pack ... now I can't clone the repository and get the following:

remote: fatal: Out of memory? mmap failed: Cannot allocate memory remote: aborting due to possible repository corruption on the remote side. fatal: early EOF error: git upload-pack: git-pack-objects died with error. fatal: git upload-pack: aborting due to possible repository corruption on the remote side. fatal: index-pack failed

How do I deal with this?   I'm running git version 1.6.2.3

I've looked at "git repack --max-pack-size", but which that created new packs it didn't delete the old monster. If I run gc, how do I tell it about the max-pack size? It doesn't seem to support this argument.

Cheers, Geoff

--
6 Fifth Ave,
St Morris, S.A. 5068
Australia
Ph: 041 8805 184 / 08 8332 5069
http://perfidy.com.au
Next: Shawn O. Pearce
Message 1 of 7 in “Large pack causes git clone failures ... what to do?”
  1. Geoff RussellAug 31, 2010
  2. Shawn O. PearceAug 31, 2010
  3. Geoff RussellAug 31, 2010
  4. Geoff RussellSep 1, 2010
  5. Geoff RussellSep 1, 2010
  6. Shawn O. PearceSep 1, 2010
  7. Geoff RussellSep 6, 2010

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.