From owner-freebsd-current@FreeBSD.ORG Thu Sep 17 16:20:52 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10199106566B for ; Thu, 17 Sep 2009 16:20:52 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id BBF078FC13 for ; Thu, 17 Sep 2009 16:20:51 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAI/+sUqDaFvG/2dsb2JhbADgHIQcBYFY X-IronPort-AV: E=Sophos;i="4.44,404,1249272000"; d="scan'208";a="48389601" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 17 Sep 2009 12:20:50 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id D82242101AD; Thu, 17 Sep 2009 12:20:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSA3KYyY-ELx; Thu, 17 Sep 2009 12:20:50 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 7418F210177; Thu, 17 Sep 2009 12:20:49 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8HGQHI19688; Thu, 17 Sep 2009 12:26:18 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 17 Sep 2009 12:26:17 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: John-Mark Gurney In-Reply-To: <20090917035141.GI861@funkthat.com> Message-ID: References: <20090917035141.GI861@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Re: NFS NLM issues w/ 8.0-BETA4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 16:20:52 -0000 On Wed, 16 Sep 2009, John-Mark Gurney wrote: > I noticed this on 7.2-R and realized that I should try this on 8.0-BETA4 > since it's about out. I think there is an issue w/ netbooting and NFS > locking. > > I setup a netboot server to export root via NFS. I took the 8.0-BETA4 > live cd, and extracted it to the root directory of the machine. Just > to keep things simple, I didn't do any configuration of the image and > booted to single user mode. I ran rpcbind, rpc.statd and rpc.lockd. > When I ran rpc.lockd, I get the following: > NLM: failed to contact remote rpcbind, stat = 3, port = 28416 > NLM: failed to contact remote rpcbind, stat = 3, port = 28416 > Can't start NLM - unable to contact NSM > > 28416 is 111 endian swapped, but that could be an artifact of not > swapping before printing it. > I think from a quick glance at the sources that you are correct, in that it is just the printf() printing it in net byte order. (I think a ntohs() should be added to the printf() arguement at some point.) I don't know why it wouldn't be able to talk to the lock manager on the server, but you might just want to try the "nolockd" option on the root mount (I don't do diskless NFS mounts, so I don't know how that option can be set?). In general, I will mention that my bias is to avoid the nlm because I believe the protocol was poorly designed. You only need it when there are apps. that do byte range locking are accessing NFS mounted files concurrently from multiple clients. If you don't need this, you don't need to run rpc.statd and rpc.lockd and, if client apps. want to do byte range locking you can use the "nolockd" option (called "nolock" on Linux). rick