berkeley db errors while appending string for filesystem

[Ma...@etas.de]

Hi,

I'm running subversion on a Debian system (subversion (deb 1.0.5-1), 
berkeley (deb 4.2.52-16) with repository access only via http protocol, so 
the user would be "www-data". The filesystem is ext3, disk space is big 
enough.

We ran the repository without problems for months now (size approx 1.5 
GB), but within the last two days we suddenly got plenty db problems 

berkeley db error while appending string for filesystem 
/var/lib/svn/repos/db
DB_RUNRECOVERY : fatal error, run databas recovery 

checking the db, I realized that the size has increased to ~8GB in the 
meantime (seemingly within a very short time). the ext3 filesystem limit 
is far beyond (16 TB I think) and the berkeley db max size should be 
something between 2 and 256 TB, I think. But I can't think of any other 
reason for the suddenly arising problems.
svnadmin recover worked fine, and I also removed the pending transactions 
resulting from those errors, but nearly every other checkin results in a 
db error (svnlook works without problems)

Has anybody experience with very large repositories or are there known 
problems??

And, is there a way to find out what transaction caused a certain db 
increase (i.e. which checkin added how much data)? 


Mit freundlichen Grüßen / with regards

Markus Gebhardt


ETAS/ESC-ES
Borsigstrasse 14
D-70469 Stuttgart
Tel. +49 (0)711 89661 278
markus.gebhardt@etas.de