On Oct 12, 2004, at 11:21 AM, kfogel@collab.net wrote:
> Dave Camp <dave@thinbits.com> writes:
>> What do I do now? Neither of the suggested commands seems to get very
>> far?
>
> What happens if you try '/path/to/Berkeley/bin/db_recover -c'? (We
> really ought to have a "catastrophic" recover switch available to
> 'svnadmin recover', but apparently we don't, sigh.)
I tried the following:
# 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+).
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 13 05:02:36 2004