database destroyed

Hello,

yup, the subject says it all and it is not for the first time it
happened to me.
I am having a cron script setup to make an automated backup of the database
via the 'svnadmin dump ...'

When (just by accident) someone operates with the database - co/up, while
dumping the database, it somehow gets always corrupt (so I have to run
db_recover on it) or worse, the db/__db.001 ... 005 simply just disappear.
The only cure I know is to svnadmin load the dump back in to regain
working repository :-(

and I am really not sure, why the 'svnadmin dump' needs RW access to the
database?

This is from the error.log when I was doing a whole tree checkout and
somewhere in
the middle cron started dumping the database. The dump finished
successfuly, but in
the moment it ended, everything went south....

[Wed Nov 27 00:06:48 2002] [error] [client 212.20.99.170] Could not fetch resource information. [500, #0]
[Wed Nov 27 00:06:48 2002] [error] [client 212.20.99.170] Could not open the SVN filesystem at /devel/svn/repos [500, #160029]
[Wed Nov 27 00:06:48 2002] [error] [client 212.20.99.170] (17)File exists: Berkeley DB error while opening environment for filesystem /devel/s
vn/repos/db:
DB_RUNRECOVERY: Fatal error, run database recovery [500, #160029]

after that, the ___db.00[1-5] files were missing in action :-(

Apache 2.0.43, Subversion 0.14.5-1 Debian package, Linux i686

Anyone experienced this? I am really clueless what could be wrong :-(

Regards,
Petr

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 27 00:50:24 2002