Jay Cornwall wrote:
> Hi,
>
> I have a Subversion repository set up that seems to become corrupt with
> alarming regularity. When this happens, the web interface gives this error:
>
> "Could not open the requested SVN filesystem"
>
> Attempting to recover the repository with the svnadmin fails, giving
> this error:
>
> "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 81 689286 failed on backward pass
> svn: bdb: PANIC: Cannot allocate memory
> svn: bdb: PANIC: fatal region error detected; run recovery"
From an earlier post:
"""
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 17571 340797 failed on backward pass
svn: bdb: PANIC: Cannot allocate memory
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
...
In a different test repository when I had this problem I bumped up the
DB_CONFIG values to look like this:
set_cachesize 0 8388608 8
set_lg_regionmax 524288
set_lg_bsize 2097152
set_lg_max 8388608
"""
I was getting a very similar error message to yours and fixed it by
adjusting DB_CONFIG to the above values. After changing DB_CONFIG, the
recover succeeded. For me, even when I was getting this error message
from recover, the repository was not wedged and functioned normally. YMMV.
- Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 19 10:00:06 2004