You do have backups right??!!!!! If not, you may be stuck. Everytime i had a
fatal BDB error, I couldn't get the repository back no matter what, so
switched to using fsfs and rebuilt with weekly full + nightly incremental
backups, and not much was lost.
Backups are a life saver...! The scripts in the pragmatic programmer book
are perfect, and i'm sure there are hundreds of variants around on this
list.
On 10/20/05, Gregory Youngblood <greg@netio.org> wrote:
>
> 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.9with 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
> recovery
>
> 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
> back?
>
> Thanks,
> Greg
Received on Thu Oct 20 18:27:25 2005