Bug 196192 - failok option in /etc/fstab is not honored by fsck
Summary: failok option in /etc/fstab is not honored by fsck
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.0-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-22 14:58 UTC by Anton Yuzhaninov
Modified: 2014-12-22 14:58 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Yuzhaninov 2014-12-22 14:58:16 UTC
I have servers with failok option in /etc/fstab, like

/dev/ada3 /spool/3 ufs rw,noatime,noexec,failok 0 2

I expect, that server can boot if ada3 fails.

In practice server fails to boot and drops to single used mode with message like:

THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
        ufs: /dev/ada3 (/spool/3)
Unknown error; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!

In fstab(5) failok documented as:

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.

But this option is not useful without fsck support.

How to fix:

fsck -p should ignore non-existing (non-readable) device for mount points with "failok" option.