[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: MacOS X problems---Corrupt repository

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-08-04 01:56:54 CEST

Robert Spier wrote:

>>That's correct. It is positively critical that you never run
>>'svnadmin recover' on a repository that is in use by any processes.
> Isn't that why it gets an exclusive lock?
> $ svnadmin recover /tmp/t
> Acquiring exclusive lock on repository db.
> Or is that not going to protect you from shooting yourself in the
> foot?[1]

It's not a simple problem, because svnadmin recover needs to be able to
handle the case where the client has crashed while holding the lock, so
at least some of the time it needs to forcefully break the lock. This
is a bad thing (tm) if the other process actually is still running. The
current code doesn't handle this especially well (it just breaks the
lock all the time, rather than trying to acquire it normally), so we
should definately be doing something else, the question is what?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 4 01:57:37 2003

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.