Hi,
I've been running svn on several projects for a long time and been very
happy with it. However, now I seem to have problems with several of my
repositories and I can't seem to get back to a consistent db state. Here
is a transcript of what I've tried:
svn@trind repos $ svnadmin dump rubysharp > dump_rubysharp
svn: Berkeley DB error while opening 'nodes' table for filesystem
rubysharp/db:
DB_RUNRECOVERY: Fatal error, run database recovery
svn@trind repos $ svnadmin recover rubysharp
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
svn@trind repos $ db_recover -h rubysharp/db
db_recover: Ignoring log file: rubysharp/db/log.0000000023: unsupported
log vers
ion 7
db_recover: PANIC: Invalid argument
db_recover: DBENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
svn@trind repos $ db_recover -V
Sleepycat Software: Berkeley DB 3.2.9: (January 24, 2001)
svn@trind repos $ svnadmin --version
svnadmin, version 1.0.0
compiled Mar 25 2004, 02:23:49
Copyright (C) 2000-2004 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
Granted, I haven't been updating the subversion version so I'm still at
1.0 but do I really have to scrap my changes from the last week and
restart from the latest backupped state (ok, I should take backups more
often but anyway)? This is not good; I don't want to be forced back to cvs!
I'd also be interested in knowing what could have caused this.
Thanks for any ideas,
Robert Feldt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 25 23:35:07 2004