[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

db_recover fatal error, is repo lost?

From: Gregory Youngblood <greg_at_netio.org>
Date: 2005-10-20 17:25:36 CEST

Bad BDB errors - how can I recover from this?

Continuing from my previous request for help on recovering my
repository, I used VMware and went to an older install where I built
subversion 1.0.9 with db 4.1.25. This matches the installed software
from my repository that I recovered from backup. I have two repos.

Using this method, I was able to svnadmin dump one of them succesfully.
But, not the second, larger one. And, of course, not the one I want back
the most.

First I tried svnadmin dump. It produced a very small dump file (195
bytes) with 0 revisions. svnadmin recover didn't seem to do anything
either. So, I tried db_recover. This is what I got:

db_recover: Finding last valid log LSN: file: 444 offset 658689
db_recover: Recovery starting from [1][28]
db_recover: DB_LOGC->get: invalid log record header
db_recover: PANIC: Input/output error
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database

Something tells me it's really bad when running db_recovery to be told
to run database recovery on a fatal error.

Is this repo lost to all time? Or is there something I can do to get it

Received on Thu Oct 20 17:35:24 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.