From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 00:26:37 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03F5A106566B for ; Sun, 12 Sep 2010 00:26:37 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id B60588FC0A for ; Sun, 12 Sep 2010 00:26:36 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAHu7i0yDaFvO/2dsb2JhbACDGJ8hrRmRCIEigyd0BIog X-IronPort-AV: E=Sophos;i="4.56,353,1280721600"; d="scan'208";a="91551508" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Sep 2010 20:26:35 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id E306BB3F34; Sat, 11 Sep 2010 20:26:35 -0400 (EDT) Date: Sat, 11 Sep 2010 20:26:35 -0400 (EDT) From: Rick Macklem To: Tim Kientzle Message-ID: <2141503959.776811.1284251195858.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-current@freebsd.org Subject: Re: Experimental NFS server oddity 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: Sun, 12 Sep 2010 00:26:37 -0000 > On Sep 11, 2010, at 4:20 PM, Rick Macklem wrote: > > >> I just tried adding > >> > >> nfsv4_server_enable="YES" > >> > >> to my rc.conf and found that after I rebooted the server, my > >> FreeBSD 8 > >> client (still using NFSv3) couldn't connect because there was no > >> RPC > >> mapping for nfs. > > > Did you specify both of these in rc.conf? > > nfs_server_enable="YES" > > nfsv4_server_enable="YES" > > > > You need to specify both of them (and nfsuserd="YES" if you going to > > use > > NFSv4). See "man nfsv4" for more. > > Both specified, as well as > rpcbind_enable="YES" > > > If you did specify both, then do a "ps axHl" to see what didn't > > start up. > > rpcbind, mountd, and nfsuserd are all running, but nfsd is not > running. > > > You can also look in /var/log/messages to see if any of the daemons > > are complaining about something. > > Only warning I see on a system reboot is: > nfsd: can't open /var/db/nfs-stablerestart > > Creating this file and then rebooting the system seems to get things > working. > > This file certainly wasn't required by the old nfsd. > Should this file be created by /etc/rc.d/nfsserver at boot time (if it > doesn't exist)? > Or should it be created by installworld? > Technically, it should only be created for a fresh install on a disk that has never been set up before. (ie. Not on an update/upgrade unless it has never existed before.) If this file is lost during a crash, the technically correct thing is to recover it from backups and not let the server start until it is recovered, since the information in it is critical to a correct reboot recovery of the NFSv4 state. So the answer is "no" for /etc/rc.d/nfsserver unless you don't care about correct server crash recovery. I don't know if installworld can differentiate between a fresh install and an upgrade? (I suppose it could create it if it doesn't already exist.) As such, I just documented it in "man nfsv4" for now, rick