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

Re: database destroyed

From: Petr Sebor <petr_at_scssoft.com>
Date: 2002-11-28 01:24:37 CET

On Wed, Nov 27, 2002 at 05:40:45PM -0600, Ben Collins-Sussman wrote:
> Petr Sebor <petr@scssoft.com> writes:
>
> Did you see the "Please stand by..." just sit there, and then assumed
> it was hung? It wasn't. It was actually running recovery, which can
> take anywhere from 5 seconds to 5 minutes. 'svnadmin recover' never
> waits on an exclusive lock. It *assumes* that you, the user, are 100%
> certain that no other processes are accessing the db, and then
> *forcibly* removes any locks sitting in the repository before starting
> recovery.
>
> I think the problem here is that the actual recovery phase isn't
> giving the user any feedback that it's working. :-(

Well, gave it about 15 minutes once.. nothing. strace svnadmin stopped
at a function that tried to lock the db.lock file, but no one was
accessing the repository at that time)

I know the svnadmin shows no output, but I am being patient. When
top shows there is an activity, I'll wait waiting happily for it
to finish. Thats not the problem...

> Stop using svn 0.14.X. These memory bugs were fixed in 0.15, and
> we're about to release 0.16 next week.

Oops... yes, I am still using the prepackaged debian 0.14.5-1

I'll either wait for the 0.16 package or try the latest from
CVS.. oops .. SVN :-)

Thanks,
Petr

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 28 01:32:53 2002

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.