conf/186032: failok option in /etc/fstab not being honored when NFS export is unavailable
Brian O'Regan
briano at bossbox.com
Thu Jan 23 12:20:00 UTC 2014
>Number: 186032
>Category: conf
>Synopsis: failok option in /etc/fstab not being honored when NFS export is unavailable
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jan 23 12:20:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Brian O'Regan
>Release: 10
>Organization:
>Environment:
FreeBSD basebsd10 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root at snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
When attempting to boot FreeBSD 10 when we try to mount an export that is not currently available the boot process stalls at [tcp] 192.168.1.2:/x: RPCPROG_NFS: RPC: Program not registered and loops until the export becomes available.
fstab(5) documentation mentions:
"If the option ``failok'' is specified, the system will ignore any error
which happens during the mount of that filesystem, which would otherwise
cause the system to drop into single user mode.
"
My expectation is if we set failok we should ignore the RPC error and continue to boot.
root at basebsd10:/var/log # cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/da0p2 / ufs rw 1 1
/dev/da0p3 none swap sw 0 0
192.168.1.2:/x/x /mnt/x nfs rw,failok 0 0
>How-To-Repeat:
Point /etc/fstab to an export that is not available and boot the machine.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list