Petr Sebor <petr@scssoft.com> writes:
> I don't know why, but I am unable to use svnadmin recover most of
> the time. I says it is waiting for the exclusive lock and if not
> manually killed, it would wait forever it seems. But there is no one
> sitting at that lock according to lsof (hope that locks/db.lock is
> the proper file) and running the recovery by hand succeeds.
'svnadmin recover' shows this output:
Acquiring exclusive lock on repository db, and running recovery procedures.
Please stand by...
Recovery completed.
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. :-(
> Another strange thing is that I am getting OOM quite often on update
> process... last time I tried updating a directory of 1136 files
> (total of ~5.6MB of sources), according to 'top' it ate 302MB of
> memory. (the update was getting a whole new directory with that
> number of files)... on a machine with 256MB of physical memory and
> 128MB swap, I am simply unable to update my source tree :-) I had to
> shot down KDE & X to get somewhere and even then it was close :-)
Stop using svn 0.14.X. These memory bugs were fixed in 0.15, and
we're about to release 0.16 next week.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 28 00:44:12 2002