We experienced a subversion database corruption. We are not entirely sure what caused it, but after the corruption all attempts at reading, writing, or recovering our database froze in what appeared to be a failure to get a lock. Reproducible: Always Steps to Reproduce: 1. 2. 3. Looking through the debian bug database I found this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185033 with an accompanying patch to libdb. After some discussion with the svn developers, they indicated debian has an extra patch that was not officially published by sleepycat. See http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=38961. I'm not familiar enough with the gentoo to know if these are appropriate to apply against either libdb or what appears to be a statically linked version of libdb4.0. Also, it seems the svn developers are suggesting libdb4.1 for recent versions. I'll leave it in your capable hands.
grant seems like a db issue?
Tossing to pauldv, since my vague recollection is that he's better suited.
Unfortunately subversion still freaks out sometimes. It is almost impossible though to find out why. The best solution normally is to try a newer version.
A couple of subversion and db versions later I guess this can be closed
