misc/145910: Problem with nullfs in fstab on boot
yanefbsd at gmail.com
Wed Apr 21 13:10:04 UTC 2010
The following reply was made to PR misc/145910; it has been noted by GNATS.
From: Garrett Cooper <yanefbsd at gmail.com>
To: Alexander Yamshanov <alexander at yamshanov.ru>
Cc: freebsd-gnats-submit at freebsd.org
Subject: Re: misc/145910: Problem with nullfs in fstab on boot
Date: Wed, 21 Apr 2010 06:00:58 -0700
On Wed, Apr 21, 2010 at 2:08 AM, Alexander Yamshanov
<alexander at yamshanov.ru> wrote:
> System with 'nullfs' in fstab can't boot without root's help because it c=
an't exec fsck_nullfs on startup.
>> grep nullfs /etc/fstab
> /export/home =A0 =A0 =A0 =A0 =A0 =A0/usr/home =A0 =A0 =A0 nullfs =A0rw =
=A0 =A0 =A0 =A0 =A0 =A0 =A02 =A0 =A0 =A0 2
> Simple fix - create file /sbin/fsck_nullfs:
>> more /sbin/fsck_nullfs
> exit 0
So given the logic provided, there should also be dummy fsck
scripts for other filesystems not fsck supported then?
$ ls -1 /sbin/fsck_* /sbin/mount_*
I personally think that this is already taken care of in the
documentation for fstab(5):
The fifth field, (fs_freq), is used for these file systems by the dump=
command to determine which file systems need to be dumped. If the fif=
field is not present, a value of zero is returned and dump will assume
that the file system does not need to be dumped. If the fifth field i=
greater than 0, then it specifies the number of days between dumps for
this file system.
If the sixth field is not present or is zero, a value of zero is retur=
and fsck(8) and quotacheck(8) will assume that the file system does no=
need to be checked.
So if the values of the 5th and 6th fields in your fstab are 0,
then this is a non-issue. I just don't personally see the real value
in adding 8 extra dummy fsck scripts (only msdosfs and ufs have fsck
binaries) as this is logically a non-issue provided the documentation
More information about the freebsd-bugs