Date: Mon, 8 Feb 2010 10:08:43 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: NFSv4: mount -t nsf4 not the same as mount_newnfs? Message-ID: <Pine.GSO.4.63.1002081001390.25952@muncher.cs.uoguelph.ca> In-Reply-To: <4B6FE550.9020506@zedat.fu-berlin.de>
index | next in thread | previous in thread | raw e-mail
On Mon, 8 Feb 2010, O. Hartmann wrote: > > Mounting the filessystem via > > mount_newnfs host:/path /path > Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that apps/daemons running locally on the server won't see byte range locks performed by NFSv4 clients.) However, byte range locking between NFSv4 clients should work ok. rickhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002081001390.25952>