Cascade of problems and mistakes has lead to a corrupt DB. I hoping there is
some way to fix this. Running svnadmin, version 1.2.1 (r15230) which uses
bdb 4.3 on Win 2003 Server.
First we had a full disk and svn stopped working. I freed disk space and
then unfortunately ran "svnadmin recover" without stopping Apache. Not sure
if anyone was accessing the DB, but they could have been (as an aside it
sure would be nice if something that can corrupt the DB would say "are you
sure the repos is detached y/n:" before starting).
Anyway, the recover failed so I am now trying db_recover and that fails
also. The output of db_recover is below. Any hope of fixing this?
C:\temp\SubversionRc\Sources\db>db_recover -c -v -h .
db_recover: unable to join the environment
Finding last valid log LSN: file: 5232 offset 282142
db_recover: Skipping log file .\log.0000001863: historic log version 8
db_recover: Skipping log file .\log.0000001323: historic log version 8
db_recover: Skipping log file .\log.0000001192: historic log version 8
db_recover: Skipping log file .\log.0000001157: historic log version 8
db_recover: Skipping log file .\log.0000001083: historic log version 8
db_recover: Skipping log file .\log.0000000965: historic log version 8
db_recover: Skipping log file .\log.0000000954: historic log version 8
db_recover: Skipping log file .\log.0000000921: historic log version 8
db_recover: Skipping log file .\log.0000000860: historic log version 8
db_recover: Skipping log file .\log.0000000788: historic log version 8
db_recover: Skipping log file .\log.0000000710: historic log version 8
db_recover: Skipping log file .\log.0000000683: historic log version 8
db_recover: Skipping log file .\log.0000000674: historic log version 8
db_recover: Skipping log file .\log.0000000622: historic log version 8
db_recover: Skipping log file .\log.0000000603: historic log version 8
db_recover: Log file corrupt at LSN: [1914][1046477]
db_recover: PANIC: Invalid argument
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
Thanks,
-Brad
Received on Fri Dec 16 02:04:18 2005