Re: Database corrupted after power failure

From: <kfogel_at_collab.net>
Date: 2004-10-13 06:24:24 CEST

Dave Camp <dave@thinbits.com> writes:
> # cd foo/db
> # /usr/local/BerkeleyDB.4.2/bin/db_recover -c
> db_recover: Ignoring log file: log.0000000002: magic number 0, not 40988
> db_recover: Invalid log file: log.0000000002: Invalid argument
> db_recover: First log record not found
> db_recover: PANIC: Invalid argument
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
> recovery
>
> At this point, I've given up. The repository was brand new (we just
> switched to subversion on Monday) so starting over wasn't a big
> deal. However, it is somewhat distressing that the database can't be
> fixed. I was under the impression that the journalling was supposed to
> prevent that... especially considering that the file system it's on is
> journaled as well (Mac OS X Server with HFS+).

Yuck.

Do you have an 'ls -lR' of the repository?

Obviously, if the OS filesystem or disk itself lost data, there's
nothing Subversion can do about it. That seems unlikely, though. An
'ls -lR' might help us detect that.