Date: Wed, 23 Nov 2011 10:26:21 -0800 From: Sean Bruno <seanbru@yahoo-inc.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: FreeBSD-Current <freebsd-current@FreeBSD.org>, Dimitry Andric <dim@FreeBSD.org> Subject: Re: NFS + SVN problem? Message-ID: <1322072781.12047.4.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <465660264.237830.1322071102401.JavaMail.root@erie.cs.uoguelph.ca> References: <465660264.237830.1322071102401.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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. Sean [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAABAgAGBQJOzTrHAAoJEL2UHwafTLtOGJwH/0mW4Uy9iaQ2AcRc0NAQkWze MFxbUw320m8XAmukp9MYvoG6PMvAQl+YZSX01sI6ERb8ItcEQIOflF8wtvR7Tm2k N5TXM3bB45gmm5kAhEgZ+7iC2rNkhvnZMlhfruH+TBS7KJfp+g4PMEicNcNFIusU QPv3LhU9f1uPh9SjKb1FddzsZRVXAdUWCgm2v2wPVbLihuoiPFugA6lAl9G5zD8v e1v2N7Is5F9rFlGMrOxnmhVjRNHA2atLAkDmIYnvXSzhQIZys/3q8psDjDY/0Nuy OEn27QUgEugO2gNTpsglYTIZ2wEptbUlpCUruDkuM6Csbvq9zf97fttzrwnU0dA= =+kkK -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1322072781.12047.4.camel>