Sunil Shetye wrote:
> Hi,
>
> "svn diff" fails when run with many filenames (more than 130 or so).
>
> $ svn diff -r 41899:41900
> [ no errors ]
>
> $ svn diff -r 41899:41900 file001 file002 ... file150
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///my/repos/trunk/file053'
> svn: Berkeley DB error while opening 'nodes' table for filesystem /my/repos/db:
> Cannot allocate memory
> svn: bdb: Logging region out of memory; you may need to increase its size
Please see this message:
http://www.contactor.se/~dast/svnusers/archive-2004-10/1001.shtml
> $ svnadmin recover /my/repos
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: Logging region out of memory; you may need to increase its size
> svn: bdb: Recovery function for LSN 5316 3252932 failed on backward pass
> svn: bdb: PANIC: Cannot allocate memory
> svn: bdb: PANIC: fatal region error detected; run recovery
> [ last line repeated 1662 times! ]
>
> [ what should one do if "svnadmin recover" tells one to run recovery? ]
>
> Luckily, "svnadmin dump" was still working, so I recovered the
> repository using hotcopy + incremental dump. I increased set_lg_max to
> 40Mb (41943040) and set_lg_bsize to 10Mb (10485760) in
> /my/repos/db/DB_CONFIG and ran "svnadmin recover". [Is there any way
> of knowing if the new values have been used during recovery?]
> Repeating the above "svn diff" command gave the same error.
Increasing set_lg_max and set_lg_bsize didn't work for me, until I added
the set_cachesize and set_lg_regionmax settings (see link) I couldn't
get recover to succeed.
- Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 29 01:15:41 2004