[Bug 196192] failok option in /etc/fstab is not honored by fsck

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196192

Bill Blake <billblake2018@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |billblake2018@gmail.com

--- Comment #1 from Bill Blake <billblake2018@gmail.com> ---
The same problem still exists in 13.0.

In my case, I have a single root file system which I share among vm's, some of
which have a /home file system and some of which do not.  I had assumed that I
could just put failok in my fstab and the vm boot would simply ignore a missing
/home.  Not so, since fsck really does want that file system to exist, failok
or no.

My workaround is to set passno to 0 in the fstab entry for the /home file
system, leaving it to code in rc.local to do the fsck only when the associated
device exists.  Kinda klugey, but it solves the problem.

Anyway, there are two reasonable approaches to dealing with this issue.  One is
to make fsck honor the failok flag.  The other is to note in the fstab man page
that, though mount honors the failok flag, fsck does not, and thus that this
flag will not guarantee a proper boot when the file system is unavailable.

-- 
You are receiving this mail because:
You are the assignee for the bug.