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

git clone out of memory. alternatives?

From
JCJeffrey Chang <jeffrey.chang@duke.edu>
Date
Mar 28, 2008, 02:29 UTC
Message-ID
<beb5fde90803271929u40a98915ifd05234476ab92f9@mail.gmail.com>
Hello,

I am working with a large-ish git repository set up as a shared repository. I am the only user of this repository, and I access it over ssh.

I am running into a problem where I can no longer clone the repository on a new computer. I get a message that seems to indicate that the machine with the repository is running out of memory.

xigua:~/remotecvs jchang$ git clone [...] Initialized empty Git repository in [...] remote: Generating pack... remote: Done counting 9122 objects. remote: Deltifying 9122 objects... error: git-upload-pack: git-pack-objects died with error. fatal: git-upload-pack: aborting due to possible repository corruption on the remote side. remote: fatal: out of memoryremote: remote: aborting due to possible repository corruption on the remote side. fatal: early EOF fatal: index-pack failed fetch-pack from [...] failed. xigua:~/remotecvs jchang$

Moving the repository to another machine is not an option, nor is adding more RAM to that machine.

Is there any way to get around this problem?  For example:
- Can I run git clone in a way that uses less memory, such as cloning
a piece of the repository at a time?
- Can I export the entire repository as a file that can be loaded on
my target machine, like "svnadmin dump" for subversion?
- Can I just rsync the repository from another computer that already has a copy?
- Are there any other work-arounds to set up a copy of the repository
on my local machine?

Thanks, Jeff

Next: Linus Torvalds
Message 1 of 3 in “git clone out of memory. alternatives?”
  1. Jeffrey ChangMar 28, 2008
  2. Linus TorvaldsMar 28, 2008
  3. Johannes SchindelinMar 28, 2008

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.