[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: Morten Mertner <morten_at_mertner.com>
Date: 2004-07-12 03:56:26 CEST

Hi Ben,

>>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
>Can you remind me of the details? It's not a shock that 'svnadmin
>recover' might not be interruptable by control-C... but couldn't you
>just open a new shell (ssh session, or local terminal, or whatever) and
>'kill -9' the process? Why did you have to reboot?
I could indeed open a new ssh session and kill the process, but without
being able to run
the svnadmin recover the repository would remain offline.

Once rebooted the recovery took about 5 seconds to complete.

If it might be of any relevance the source repository stores no secrets
(it's used for an
open source project), so I can zip it up and put it online if that might
be useful. I didn't
think of this before now so actually doing it will have to wait until it
happens again.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 12 05:52:14 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.