> From: sussman@collab.net [mailto:sussman@collab.net]
> Sent: Friday, August 01, 2003 6:58 PM
> Blair Zajac <blair@orcaware.com> writes:
>
> > To put this back on the radar screen, there has been a number of issues
> > with people using 4.1.25 on Linux/FreeBSD boxes that have had repositories
> > that end up being corrupted where the only way to recover is to restore
> > a backup copy.
>
> 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).
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 1 19:06:33 2003