Date: Sat, 27 Mar 2010 12:04:39 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: freebsd-stable@freebsd.org Subject: Re: NFS lockd problem Message-ID: <20100327190439.GA45830@icarus.home.lan> In-Reply-To: <4931283F-5B5B-4368-BB40-20B5FEBF4E17@mac.com> References: <4BAC879A.2040301@zirakzigil.org> <4931283F-5B5B-4368-BB40-20B5FEBF4E17@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 27, 2010 at 11:50:17AM -0700, Chuck Swiger wrote: > On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote: > > Outset: > > 1 NFS server (with lockd) > > 2 NFS client (with lockd) > > > > The clients serve several jails with apache, whose data (www) resides on the server > > If you need file locking to work reliably, you pretty much have to give up on using NFS + rpc.lockd and run against a local UFS filesystem. I thought fcntl(2) worked reliably/properly with NFS on FreeBSD? I remember reading somewhere how mixing locking types (fcntl vs. flock vs. lockf) causes major problems, but as long as the same locking method is used universally things should work...? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100327190439.GA45830>