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

Subversion/BerkeleyDB lock problem (part II)

From: Morten Mertner <morten_at_mertner.com>
Date: 2004-07-11 22:21:40 CEST

Hi Again,

I posted about a week ago regarding Subversion locking up the repository
needing recovery before coming back alive. I was advised to upgrade
and so I did (from 4.1.25-p1 to 4.2.52-p2).

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.

Like I said in my last report, this is a real show-stopper. Having to
reboot the server
to keep the repository alive is just, well, you know.

I'm on a Gentoo Linux running a gentoo-patched 2.6.7 kernel, using
1.0.4 with patches "subversion-db4" and "subversion-1.0.4-pre-1.0.5".

Packages are compiled for generic i686 using CFLAGS "-march=athlon-xp
-O2 -pipe
-fomit-frame-pointer" (unless overridden in the gentoo package ebuilds;
the maintainers disable compile options to bypass options that would
break packages).

The problem has been present ever since 0.37 (when I first installed
although with increasing frequency in the last 2 months.

Any help in resolving this is highly appreciated!


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