Hi!
On Wed, Dec 02, 2009 at 02:07:38PM -0600, Jonathan Nieder wrote:
> Adam Borowski wrote:
> > When running "git svn clone" on a large repository, every a few revisions
> > or a single big one it stops with:
> >
> > fatal: unable to run 'git-svn'
> >
> > git svn fetch resumes the clone, stopping again after a few revisions. If
> > you keep resuming it long enough, the clone ultimately succeeds.
>
> Hmm. That message means that git found a git-svn executable but failed to
> run it for some reason, for example because the fork() system call failed.
New git says instead:
error: git-svn died of signal 13
(that's SIGPIPE)
> Just a hunch, but: what is the state of your vm.overcommit_memory setting
> (/proc/sys/vm/overcommit_memory)?
0
The system doesn't use much of its physical memory, and there's 5.5GB of swap
that lies untouched.
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
