Date: Mon, 22 Dec 2014 14:58:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 196192] New: failok option in /etc/fstab is not honored by fsck Message-ID: <bug-196192-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196192 Bug ID: 196192 Summary: failok option in /etc/fstab is not honored by fsck Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: citrin+pr@citrin.ru 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 =E2=80=9Cfailok=E2=80=9D 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 w= ith "failok" option. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196192-8>