From owner-freebsd-questions@FreeBSD.ORG Thu Oct 28 23:59:16 2004 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 05D5316A4CE for ; Thu, 28 Oct 2004 23:59:16 +0000 (GMT) Received: from support.xfr.com (support.jupiterhosting.com [64.255.160.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B175743D49 for ; Thu, 28 Oct 2004 23:59:15 +0000 (GMT) (envelope-from pwieckowski@gmail.com) Received: from [10.30.1.10] (unknown [64.255.167.140]) by support.xfr.com (Postfix) with ESMTP id 89C333427A5 for ; Thu, 28 Oct 2004 16:35:46 -0700 (PDT) From: Pete Wieckowski To: freebsd-questions@freebsd.org Date: Thu, 28 Oct 2004 16:59:15 -0700 User-Agent: KMail/1.6.2 References: <200410281600.28981.pete@jupiterhosting.com> In-Reply-To: <200410281600.28981.pete@jupiterhosting.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410281659.15440.pwieckowski@gmail.com> Subject: Re: 5.3RC1 - /etc/defaults/rc.conf - netfs_types & nfsv4 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: Thu, 28 Oct 2004 23:59:16 -0000 Let me explain this a little better. I know that I shouldn't need to edit edit /etc/defaults/rc.conf because /etc/rc.conf overrides the default. My question is should this be added into the CVS tree so people don't run into this problem while putting an 'nfs4' in /etc/fstab. If I were to have this in my /etc/fstab: nfstestclient-1# cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 /dev/ad0s1d /var ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 10.10.10.252:/vol/vol1 /vol/vol1 nfs4 rw,noatime,-s,-i,-b 0 0 nfstestclient-1# and I reboot the box, during bootup, my machine would errorout: ...dmesg... Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% ad0: 76319MB [155061/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/ad0s1b as swap device Starting file system checks: /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 236182 free (1390 frags, 29349 blocks, 0.5% fragmentation) /dev/ad0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 506276 free (28 frags, 63281 blocks, 0.0% fragmentation) /dev/ad0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 34574399 free (36079 frags, 4317290 blocks, 0.1% fragmentat) /dev/ad0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1d: clean, 1012721 free (97 frags, 126578 blocks, 0.0% fragmentation) nfs4: /vol/vol1: Can't assign requested address Mounting /etc/fstab filesystems failed, startup aborted Boot interrupted Enter full pathname of shell or RETURN for /bin/sh: ...... This is due to the fact that the system is trying to mount the NFSv4 filesystem before the network stack is up (as per /etc/rc.d/mountcritlocal). If NFSv4 is stable code under the 5.3-tree, then it may be wise to add 'nfs4' to '/etc/defaults/rc.conf' under the 'netfs_types' option. Now I'm not exactly sure if NFSv4 client support is fully stable because I believe it might be issuing a MNT_IGNORE flag, I'll look at the source to verify. If I add: extra_netfs_types="nfs4", the system boots up happily and I can see the filesystem is mounted: nfstestclient-1# mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) 10.10.10.252:/vol/vol1 on /vol/vol1 (nfs4, noatime) nfstestclient-1# Thanks, Pete Wieckowski On Thursday 28 October 2004 16:00, Pete - Jupiterhosting wrote: > I ran into this problem while mounting a netapp with nfsv4 during a reboot. > Should /etc/defaults/rc.conf have "nfs4" in the "netfs_types" list? I know > I can add it to the "extra_netfs_types" variable under /etc/rc.conf, but if > it's stable code, then it might be wise to add it into the defaults before > -RELEASE comes out. > > Thanks, > Pete Wieckowski > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"