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

Repository instability

From: Jay Cornwall <jay_at_esuna.co.uk>
Date: 2004-10-17 19:43:03 CEST

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"

A further attempt to recover the repository with the command 'db_recover
-vech /var/svn/repos/db' gives the error:

"db_recover: Finding last valid log LSN: file: 81 offset 747054
db_recover: Recovery starting from [79][28]
db_recover: Logging region out of memory; you may need to increase its size
db_recover: Recovery function for LSN 81 690040 failed on backward pass
db_recover: PANIC: Cannot allocate memory
db_recover: PANIC: fatal region error detected; run recovery"

The repository itself is quite small and subject to very low user
interaction. The interfaces I have available are:

file:/// - Local access
http:// - Apache, read-only access
https:// - Apache, read/write access

The repository doesn't need any commits to be made in order to become
corrupted, and I know local access hasn't been used between repository
corruptions.

I did have some trouble a while back with Apache running as umask 022,
causing similar problems; I've now rectified this and ensured that all
DB files are group-writable even after corruption.

The only regular activity which occurs in my repository is a nightly
'svnadmin hotcopy', again with the correct umask set. Could this be
causing the repository to corrupt itself?

Software running:

Subversion 1.1.0
DB 4.2.52
Apache 2.0.52

Any ideas?

-- 
Jay
http://www.esuna.co.uk/ - Coming soon, community blogging at its best!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 17 19:43:31 2004

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

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