From owner-freebsd-stable@FreeBSD.ORG Wed Apr 4 16:08:09 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C780216A411 for ; Wed, 4 Apr 2007 16:08:09 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id A94BE13C4AE for ; Wed, 4 Apr 2007 16:08:09 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 813121A4DA1; Wed, 4 Apr 2007 09:08:09 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B919851588; Wed, 4 Apr 2007 12:08:08 -0400 (EDT) Date: Wed, 4 Apr 2007 12:08:08 -0400 From: Kris Kennaway To: Thomas David Rivers Message-ID: <20070404160808.GA60087@xor.obsecurity.org> References: <20070404054219.ejuvhtdq8wc04ogk@webmail.1command.com> <200704041309.l34D9da90685@lakes.dignus.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <200704041309.l34D9da90685@lakes.dignus.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org, chris#@1command.com Subject: Re: NFS == lock && reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2007 16:08:09 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 04, 2007 at 09:09:39AM -0400, Thomas David Rivers wrote: > Hi Chris, >=20 > Well - the NFS server is 4.5-RELEASE - a rather old box. >=20 > Everything worked fine when the shop was all 4.x boxes, but as soon > as we put in a 5.x or 6.x box - the NFS clients on those (5.x/6.x) boxes > locked up hard if rpc.lockd was running on the 4.5-RELEASE server. >=20 > On 4.x, rpc.lockd doesn't start automatically - since, as I understand= =20 > it, rpc.lockd had "issues" in that timeframe. But, one of the developers > here turned it on hoping to get real locking for /var/mail. >=20 > So - I thought my problem might simply be the old rpc.lockd > implementation in 4.x, and I didn't worry about it (since 4.x is > out-of-service anyway.) >=20 > However, this sounded _so_ familiar - I thought I would pop-up > and mumble something like a "me too." >=20 > rpc.statd isn't running on the 4.5 NFS server. AFAICR rpc.lockd was fine in 4.x, it just wasn't a real rpc.lockd. The issues are with the rewrite that came in 5.x to add real locking, which sort of works except when it doesn't. Kris --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGE81nWry0BWjoQKURAls5AJ9Vm4bVzDwEtW3GYHzXoJl1NSwZZACfShZ3 nL+4qAlJiufbDiiWc0m4KMk= =XGqB -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--