From: Eric Wong <normalperson@yhbt.net>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn -- out of memory
Date: Sun, 15 Feb 2009 16:38:35 -0800 [thread overview]
Message-ID: <20090216003835.GA5687@untitled> (raw)
In-Reply-To: <1234608003.115771.3468.nullmailer@beryx.hq.kred>
"Alfred M. Szmidt" <ams@gnu.org> wrote:
> Hi,
>
> when doing a `git svn clone' on a subversion repository that contains
> a large file (>1GiB), `git svn' dies with the following:
>
> ams@trillian:~$ git svn clone REPO -T trunk -b branches -t tags
> [...]
> fatal: Out of memory? mmap failed: Cannot allocate memory
> hash-object -w --stdin-paths: command returned error: 128
>
> error closing pipe: Bad file descriptor at /usr/local/bin/libexec/git-core//git-svn line 0
> error closing pipe: Bad file descriptor at /usr/local/bin/libexec/git-core//git-svn line 0
>
> Doing a `git repack' doesn't help either. Anyone got a clue how to
> either solve, or work around this?
>
> git version 1.6.1.3
Hi Alfred,
Core git requires objects to be able to fit into (virtual) memory.
Adding more swap space should solve the problem for you, but this is not
only a git-svn problem.
Fwiw, git-svn itself has always had a pretty strict "no slurping"
policy.
--
Eric Wong
next prev parent reply other threads:[~2009-02-16 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 10:40 git-svn -- out of memory Alfred M. Szmidt
2009-02-16 0:38 ` Eric Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-16 9:37 Alfred M. Szmidt
2009-02-16 10:05 ` Junio C Hamano
2009-02-16 13:45 ` Jeff King
2009-02-16 14:23 Alfred M. Szmidt
2009-02-16 15:37 ` Jeff King
2009-02-16 14:52 Alfred M. Szmidt
2009-02-16 14:57 ` Sverre Rabbelier
2009-02-16 15:39 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090216003835.GA5687@untitled \
--to=normalperson@yhbt.net \
--cc=ams@gnu.org \
--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.
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 NNTP newsgroup(s).