On Sun, 2004-09-12 at 22:29, Sean Moss-Pultz wrote:
> On Sep 13, 2004, at 10:20 AM, Scott Palmer wrote:
> > I was just reading through the 1.1 release notes and the blurb about
> > the pros and cons of 'fsfs'. It seems that at least for my purposes
> > 'fsfs' is superior. I know the others in my office would not tolerate
> > a database that would need to be un-wedged every so often.
> I've been running subversion for a little over a year now and about 6
> months in a production environment. I've yet to see a wedged
> repository. We used both linux and windows servers. I really don't
> think wedging happens as much as you think it will.
We've been running svn (1.0.x) for about 6 months now, and are generally
very happy. We have experienced the wedged repository problem a number
of times (maybe ~10 now). In each case, the recovery commands have
worked (only one - the first, alas) required the db4 recover command;
the rest have been cleared up by using the svnadmin recover.
We are running a RH3 Linux server, with all external svn usage through
Apache (http and https). The only file access is either the (apache
user crontab) backup scripts (which use svn dump) and the ViewCVS script
(running under the same apache). We have a few people with the
requisite access to the server who've been taught how to unwedge it, and
have not had an outage longer than a couple of hours before one of them
could be found.
I would very much like to remove the potential for the problem, though.
If the developers would like data points (tar files of wedged
repositories with the accompanying apache logs or whatever), I suspect I
can supply them over time (I've had 3 this week - worst week ever -
feeling a bit nervous today). I'd planned to move up to 1.1 at the
'final' release anyway; if the fsfs backend isn't subject to this
problem or an equivalent, then I may take the trouble to switch that
then too (I assume that can be done with just a dump/load cycle).
SIPfoundry server tools maintainer
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Sep 13 04:49:59 2004