Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Dec 2011 10:53:15 -0500 (EST)
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        Dimitry Andric <dim@FreeBSD.org>
Cc:        FreeBSD-Current <freebsd-current@FreeBSD.org>, Sean Bruno <seanbru@yahoo-inc.com>
Subject:   Re: NFS + SVN problem?
Message-ID:  <1606093949.138320.1323791595198.JavaMail.root@erie.cs.uoguelph.ca>
In-Reply-To: <4EE70514.1040907@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Dimitry Andric wrote:
> On 2011-11-23 19:26, Sean Bruno wrote:
> > On Wed, 2011-11-23 at 09:58 -0800, Rick Macklem wrote:
> >> I don't know if Dimitry tried this, but you could also try the
> >> "nolockd" option, so that byte range locking is done locally in
> >> the client and avoids the NLM.
> >>
> >> Good luck with it and please let us know how it goes, rick
> >
> > This seems to allow SVN 1.7 to do whatever nonsense it is trying to
> > do.
> > I've modified my fstab on the test host in the cluster to:
> >
> > dumpster:/vol/volshscratch /dumpster/scratch nfs
> > rw,soft,intr,bg,nolockd,nosuid 0 0
> >
> > Removing soft,intr had no effect. This, I suspect will be
> > problematic
> > for clusteradm@ if we start updating hosts in the cluster.
> 
> A very late addition to this: I got Subversion 1.7 to work properly
> over
> NFSv3, by making sure rpc.lockd runs on both server and client.
> 
> E.g, set rpc_lockd_enable to YES in rc.conf; this is off by default,
> even if you have nfs_client_enable/nfs_server_enable set to YES.

and rpc_statd_enable="YES" on all systems, as well.

> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1606093949.138320.1323791595198.JavaMail.root>