[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: FW: Cannot allocate memory?

From: Sander Striker <striker_at_apache.org>
Date: 2002-04-11 16:52:10 CEST

> From: Ben Collins [mailto:bcollins@debian.org]
> Sent: 11 April 2002 16:37

> On Thu, Apr 11, 2002 at 02:49:01AM -0700, Greg Stein wrote:
>> ----- Forwarded message from issues-reject-1018489427.6282.fhpmcgndkcbdahfigbbg@subversion.tigris.org -----
>>
>> From: Chia Shee Liang <sheeliang@lit.org.sg>
>> Subject: Cannot allocate memory?
>> To: issues@subversion.tigris.org
>> Date: Thu, 11 Apr 2002 09:47:52 +0800
>>
>> I'm new to subversion and I'm trying to import the linux-2.4.18 kernel
>> into a local repository. I encountered an error like 'Berkeley DB
>> error length of string to long' or 'Berkeley DB error revision node
>> error' or something like that. They both end with 'Cannot allocate
>> memory'. I've tried the latest subversion from the download page as
>> well as the latest from trunk itself. Can anyone help? Please cc to me
>> as I'm not on the list.
>>
>>
>>
>> ----- End forwarded message -----
>
> Create a file called <path-to-repo>/db/DB_CONFIG, and put in it:
>
> set_lk_max_locks 5000
> set_lk_max_lockers 5000
> set_lk_max_objects 5000
>
> The do this:
>
> $ cd <path-to-repo>/db/
> $ db4_recover -ve -h .
>
> Now the import should work.

Right. Maybe we should let 'svnadmin create' create the <repos>/db/DB_CONFIG
file with some default values and put something about it in <repos>/README.
And, we should put something in the README/INSTALL file(s) about this (I'll
try and do that somewhere soon).

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 11 16:46:18 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.