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

Re: Subversion/BerkeleyDB lock problem (part II)

From: Mark Benedetto King <mbk_at_lowlatency.com>
Date: 2004-07-12 15:50:12 CEST

On Sun, Jul 11, 2004 at 10:21:40PM +0200, Morten Mertner wrote:
> Alas, it just happened again. Shutting down apache wasn't even enough
> this time,
> I had to reboot the server in order to make the "svnadmin recover"
> command not
> just hang (I waited about 5 mins and not hearing any disk activity or
> seeing the
> process being alive, I couldn't even terminate it using ctrl-c, so it
> ate the ssh session
> too). This has happened only once before and I thought it was a fluke,
> but it's
> definately related to the Subversion lockups.

svnadmin recover will block until all other locks on the repository
are released.

If you find this happening, try using "lsof" to determine which
other processes have the repository locked, and kill those ones
(while leaving the svnadmin recover running).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 12 15:50:42 2004

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

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