Karl,
Thanks for putting up this information! Unfortunately, I was never able
to get my original repository fully-recovered. Though, as I said,
through some miracle I did manage to get it to a state where I could
perform a dump, by playing stupid games with the log files.
Since power had gone down well *after* the last commit to SVN, the only
thing that seemed to have gotten corrupt was the log files themselves,
and not the db; and it seems (in the few times I've had this type of
problem) that BDB is very sensitive to corrupt log files and has
difficulty recovering from them.
Zach
On Jul 1, 2005, at 7:07 AM, kfogel@collab.net wrote:
> kfogel@collab.net writes:
>> Instead, you should try using Berkeley's 'db_recover' utility first,
>> passing it the '-c' option, meaning "perform catastrophic recovery".
>> (See http://www.sleepycat.com/docs/utility/db_recover.html.)
>>
>> Make sure nothing else is accessing the repository when you do it.
>>
>> I'm surprise to find that there is no way to tell 'svnadmin recover'
>> to do a catastrophic recovery, and that we don't seem to have a FAQ
>> item on this. I'll try to do something about the latter, at least.
>
> Okay, we have information about this in our FAQ now, see
>
> http://subversion.tigris.org/faq.html#wedged-repos
>
> (or rather, see it five minutes from now, when the live site gets the
> updates I just committed :-) ).
>
> Let us know if db_recover helped you at all.
>
> -Karl
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 1 18:17:10 2005