C. Michael Pilato <cmpilato@collab.net>:
> "Eric S. Raymond" <esr@snark.thyrsus.com> writes:
>
> > What does one do when "svnadmin recover" fails with a fatal error?
> >
> > esr@sheep:~> svnadmin recover /svnroot/repos/gpsd
> > Please wait; recovering the repository may take some time...
> > svn: DB_RUNRECOVERY: Fatal error, run database recovery
> > esr@sheep:~>
>
> Obey the instructions, of course. Oh. Wait. :-)
>
> Try running a catastrophic recover:
>
> $ /path/to/BDB4.x/bin/db_recover -vech /svnroot/repos/gpsd/db
esr@sheep:~> svnadmin recover /svnroot/repos/gpsd
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
esr@sheep:~> db_recover -vech /svnroot/repos/gpsd/db
db_recover: Finding last valid log LSN: file: 40 offset 5152
db_recover: Recovery starting from [39][28]
db_recover: /svnroot/repos/gpsd/db/log.0000000040: log file open failed: Permission denied
db_recover: PANIC: Permission denied
db_recover: DB_ENV->log_put: 40: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: txn_checkpoint: log failed at LSN [40 5070] DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: /svnroot/repos/gpsd/db/log.0000000040: log file open failed: Permission denied
db_recover: PANIC: Permission denied
db_recover: DB_ENV->log_put: 40: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
esr@sheep:~>
Do I have to be root for this? On berlios.de I'm not an admin.
--
Eric S. Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 10 01:42:19 2004