5.3RC1 - /etc/defaults/rc.conf - netfs_types & nfsv4
pwieckowski at gmail.com
Thu Oct 28 16:59:16 PDT 2004
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
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
and I reboot the box, during bootup, my machine would errorout:
Timecounters tick every 10.000 msec
acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0%
ad0: 76319MB <MDT MD800BB-00BSA0/12.08C12> [155061/16/63] at ata0-master
acd0: CDROM <COMPAQ CDR-8435/0013> 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%
/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
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:
/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)
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.
> Pete Wieckowski
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions