Berkeley DB error due to hardware problem

Hello,

probabaly due to hardware problems of our (former) repository hard
disk, one of our Subversion repositories seems to be corrupted right
now. This is situation right now: Running "svnadmin recover" runs
without any errors/complaints. However, a subsequent "commit" or
running "svnadmin verify" still leads to the following Berkeley DB
error:

Apache:
 
[Mon Jul 12 16:35:07 2004] [error] [client 132.230.151.5] (17)File
exists: Berkeley DB error while moving cursor for filesystem
/export/server/subversion/proglang/db:\nDB_PAGE_NOTFOUND: Requested page
not found [500, #160029]
 
SVN:

# svnadmin verify /export/server/subversion/proglang
* Verified revision 0.
* Verified revision 1.
svn: Berkeley DB error while moving cursor for filesystem
/export/server/subversion/proglang/db:
DB_PAGE_NOTFOUND: Requested page not found

Also, dumping parts of the repository (using revision number ranges)
seems to show that errors occur approximately every hundred or so
revision numbers.

Does anybody now how to deal with this specific Berkely DB error?

We've got a backup of the repository from a couple of days back
without errors. Is there common "emercency strategy" how to proceed in
such situations?

-Matthias

P.S. BTW, we are using svn, version 1.0.4 (r9844), under SunOS 5.9.

-- 
Matthias Neubauer                                       |
Universität Freiburg, Institut für Informatik           | tel +49 761 203 8060
Georges-Köhler-Allee 79, 79110 Freiburg i. Br., Germany | fax +49 761 203 8052
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org