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

Re: How to tell if db repo is locked?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-11-20 04:23:36 CET

Jeff Squyres <jsquyres@lam-mpi.org> writes:

> From this behavior, we're assuming that there is some stale lock
> that was left over that is causing all the commands to hang, and
> "svn recover" is able to remove it. Is that a correct assumption?


> If so, is there any way to tell that a repository has a stale lock
> and it's "ok" to just "recover"? I ask because know this may
> shorten our diagnostic time -- we'll be much less apprehensive about
> invoking "svn recover" if we have an indication that it may just be
> a stale lock and will run very quickly.

I don't think so. My experience has been that if a repos is "wedged"
(the term I prefer to use over "locked") even the Berkeley DB
utilities (save for db_recover, of course) will hang on access.
Overall, I'd say you have an unhealthy fear of 'svnadmin recover'. As
long as 'svnadmin recover' has exclusive access to the database
environment, you shouldn't be concerned about its use.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 20 04:28:14 2004

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.