From: Alexander Gladysh <agladysh@gmail.com>
To: git@vger.kernel.org
Subject: Git-SVN memory error
Date: Tue, 12 May 2009 21:04:56 +0400 [thread overview]
Message-ID: <c6c947f60905121004v257e6f72m2a24de12c98dd1ba@mail.gmail.com> (raw)
Hi, list!
I'm importing a rather large SVN repository into Git. I'm doing it on
a Synology DS508 NAS PPC box (don't ask me why :-) ). I'm getting an
out of memory error when trying to import one of commits. Please help
me to debug/workaround it.
Relevant system information below.
Alexander.
DiskStation> uname -a
Linux DiskStation 2.6.24 #839 Wed Mar 25 18:30:32 CST 2009 ppc GNU/Linux
DiskStation> git --version
git version 1.6.3
DiskStation> sudo ipkg info git
Package: git
Version: 1.6.3-1
Depends: zlib, openssl, libcurl, diffutils, rcs, expat
Suggests: git-manpages
Status: install user installed
Section: net
Architecture: powerpc
maintainer: NSLU2 Linux <nslu2-linux@yahoogroups.com>
MD5Sum: b92688e018f23fa7a82a504d073fe813
Size: 5872996
Filename: git_1.6.3-1_powerpc.ipk
Source: http://www.kernel.org/pub/software/scm/git/git-1.6.3.tar.gz
Description: GIT is a directory tree content manager that can be used
for distributed revision control.
DiskStation> free # That is actually AFTER git svn died.
total used free shared buffers
Mem: 516172 501828 14344 0 62656
Swap: 2586456 29508 2556948
Total: 3102628 531336 2571292
DiskStation> git svn fetch # This is the second run. First one failed
with the same message.
Index mismatch: ba0c6593571c2f4b6b6ceff1b1326b30d0cd9495 !=
c633473cfe3dd92e536450e48cd1d9cb2da1cdd2
rereading fe4935bc22756ffdb430f94cd7ce4af898750edb
A File1.rar
...
A FileN.rar
fatal: Out of memory, malloc failed
hash-object -w --stdin-paths: command returned error: 128
error closing pipe: Bad file descriptor at /opt/libexec/git-core/git-svn line 0
error closing pipe: Bad file descriptor at /opt/libexec/git-core/git-svn line 0
reply other threads:[~2009-05-12 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c6c947f60905121004v257e6f72m2a24de12c98dd1ba@mail.gmail.com \
--to=agladysh@gmail.com \
--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).