DB_RUNRECOVERY failed with fatal error

Hi all,

I started using Subversion this week and I really like its features in
comparison with CVS, but I was experiencing problems nearly from the
beginning, which now have resulted in a seemingly unrecoverable DB crash.
The error message I get when running the recovery is

Acquiring exclusive lock on repository db.
Recovery is running, please stand by...
Recovery completed.
svn: Berkeley DB error
svn: Berkeley DB error while opening `nodes' table for filesystem myrepos
DB_RUNRECOVERY: Fatal error, run database recovery
Aborted

The problem occured when someone else (than me, the repository owner) tried
to commit files to the repository for the first time. BTW, we're using the
filesystem client only, so no Apache etc. involved. I guess there's
something wrong with my Subversion installation, but I can't figure what it
could be (I'm not the one who did the install).
Well, as I mentioned before, there have been some other problems: I did
some commits and when my colleagues tried to update their working copies
the client aborted and I had to run a recovery. After the recovery, the
access permissions of some files in the db folder were reset so I had to do
a chmod...after that, the update succeeded.

Are these two problems interrelated? Does anyone have a clue what the root
problem may be? BTW, I'm using subversion 0.17.1 on a machine with Debian
Linux version 2.4.19. I'd be really thankful for any useful information!

Best regards,
Arne Handt

-- 
Software Development                                  EsPresto AG
-----------------------------------------------------------------
handt@espresto.com                              Breite Str. 30-31
Tel/Fax: +49.30.90 226.750/.760              10178 Berlin/Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org