Date: Sun, 28 Mar 2010 13:19:59 +0300 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: "Giulio Ferro" <auryn@zirakzigil.org>, "Chuck Swiger" <cswiger@mac.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: NFS lockd problem Message-ID: <op.u99y3lgt8527sy@pinky> 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, 27 Mar 2010 20:50:17 +0200, Chuck Swiger <cswiger@mac.com> 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 don't have this experience. I use NFS locking between FreeBSD, Linux, NetApp and SUN stuff. Older versions of FreeBSD had some troubles, but more recent ones work very well. Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.u99y3lgt8527sy>