From owner-freebsd-questions@FreeBSD.ORG Wed Feb 9 21:52:45 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1862616A4CF for ; Wed, 9 Feb 2005 21:52:45 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB04743D2F for ; Wed, 9 Feb 2005 21:52:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E1091512AF; Wed, 9 Feb 2005 13:52:43 -0800 (PST) Date: Wed, 9 Feb 2005 13:52:43 -0800 From: Kris Kennaway To: Tim Traver Message-ID: <20050209215243.GA13823@xor.obsecurity.org> References: <420A6586.1000302@simplenet.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <420A6586.1000302@simplenet.com> User-Agent: Mutt/1.4.2.1i cc: questions@freebsd.org Subject: Re: NFS File Locking across multiple machines X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 21:52:45 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 09, 2005 at 11:33:26AM -0800, Tim Traver wrote: > Hi all, >=20 > a couple of years back, we ran into a problem with the FreeBSD NFS code= =20 > where file locks were not seen by other machines. >=20 > We use Netapp disk hardware to mount NFS filesystems to our FreeBSD=20 > systems. In the past, two different machines would not recognize locks=20 > from each other, and would sometimes cause file collisions. >=20 > From the same machine, two different processes would recognize locks=20 > without a problem. >=20 > In our experience, the Sun servers that we had also did not have any=20 > problems. This was after creating specific tests to make this determinati= on. >=20 > We reported it to the freebsd developers way back when, and have lost=20 > track as to the status of the issue. >=20 > Does anyone on this list know of the developer that was developing the=20 > NFS code ??? or know anything about the issue ??? or have an answer ??? ;) >=20 > I'd like to talk to him/her to see what the status is in the later=20 > FreeBSD 4.x series as well as 5.x In 4.x and older rpc.lockd does not implement client-side locking. This is documented in the manpage. In 5.x and later rpc.lockd does do client-side locking. Kris --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCoYrWry0BWjoQKURAkvyAJ9aBK2rBszpJUZoLnfp+yzNqr9UrwCg62u7 QITU04X5ylFVA0TDvVy0F2Y= =i/x/ -----END PGP SIGNATURE----- --9amGYk9869ThD9tj--