On Wednesday, July 11, 2012 9:28:19 AM UTC+2, Sergiu wrote: > > Hi. > > I've been struggling for few days now with this, so I was hoping I could > get some suggestions here. > It's about cloning a repo. It used to work, but it just started to throw > this error when I "git clone ssh://git@hostname:10101/test.git": > > remote: Counting objects: 11401, done. > remote: Compressing objects: 100% (9278/9278), done. > select: Not enough memory4561/11401), 206.60 MiB | 1.01 MiB/s > fatal: The remote end hung up unexpectedly > fatal: early EOF > fatal: index-pack failed > > I cannot clone this repo anymore. It always dies around 206-208 MiB. > Anyone dealt with this before? Any suggestions? Thank you. > > # Server: CentOS release 6.2 (Final) 2.6.32-220.el6.x86_64 > # cat /proc/meminfo > # MemTotal: 16316936 kB (16 316 936 kilobytes = 15.5610428 gigabytes) > # MemFree: 5251088 kB (5 251 088 kilobytes = 5.00782776 gigabytes) > > Strange, I haven't seen anything like it before. First idea is that it is a memory leak in a faulty version of Git.
Can you please paste the output of *git --version*? Googling around a bit, I found these hints: * http://stackoverflow.com/questions/4826639/repack-of-git-repository-fails - you could try tweaking the packfile size configuration as in this answer * http://stackoverflow.com/questions/1590198/git-clone-memory-allocation-error - check for very large files in your repository, also run git gc on the remote * http://git.661346.n2.nabble.com/Large-pack-causes-git-clone-failures-what-to-do-td5481488.html - also an interesting discussion, regarding repack -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/CSTLsuR658cJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
