Re: MacOS X problems---Corrupt repository

On Sun, Aug 03, 2003 at 12:47:17AM -0500, cmpilato@collab.net wrote:
> "Sander Striker" <striker@apache.org> writes:
>
> > > My recollection is that Sander Striker was having discussions with
> > > sleepycat folk, and that some deep issue was revealed. In almost all
> > > of these cases, a berkeley db table had switched 'type' for some
> > > reason; the sleepycat people revealed that this might happen if
> > > recovery is happening whilst something else changes the db. (Is this
> > > accurate, Sander?)
> >
> > Let me dig up the mail. Note that a big chunk of communication was
> > done by cmpilato BTW.
> >
> > What it basically comes down to is that a recover will recreate the
> > environment. Which means that if you modify the db while recovering
> > you get an inconsistent environment (wrong allocation counts etc).
>
> That's correct. It is positively critical that you never run
> 'svnadmin recover' on a repository that is in use by any processes.

Perhaps the FAQ should be updated to recommend running hotbackup.py
before recovery?

-- 
Michael Wood <mwood@its.uct.ac.za>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org