NFS + SVN problem?
seanbru at yahoo-inc.com
Wed Nov 23 18:26:36 UTC 2011
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 490 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20111123/71e89d26/attachment.pgp
More information about the freebsd-current