Bug 186032 - failok option in /etc/fstab not being honored when NFS export is unavailable
Summary: failok option in /etc/fstab not being honored when NFS export is unavailable
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2014-01-23 12:20 UTC by Brian O'Regan
Modified: 2018-11-06 20:34 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Brian O'Regan 2014-01-23 12:20:00 UTC
When attempting to boot FreeBSD 10 when we try to mount an export that is not currently available the boot process stalls at [tcp] 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@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       /mnt/x       nfs     rw,failok       0       0

How-To-Repeat: Point /etc/fstab to an export that is not available and boot the machine.
Comment 1 Enji Cooper freebsd_committer 2015-11-15 06:06:06 UTC
I've seen this too recently. I'm wondering if dump/pass == 0 vs != 0 would affect this any..
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:53:53 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

- Set Status to "Open"