From owner-freebsd-bugs@FreeBSD.ORG Wed Apr 21 13:10:04 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43DFA106567B for ; Wed, 21 Apr 2010 13:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A1728FC28 for ; Wed, 21 Apr 2010 13:10:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3LDA3Y1040181 for ; Wed, 21 Apr 2010 13:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3LDA3PG040180; Wed, 21 Apr 2010 13:10:03 GMT (envelope-from gnats) Date: Wed, 21 Apr 2010 13:10:03 GMT Message-Id: <201004211310.o3LDA3PG040180@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: misc/145910: Problem with nullfs in fstab on boot X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2010 13:10:04 -0000 The following reply was made to PR misc/145910; it has been noted by GNATS. From: Garrett Cooper To: Alexander Yamshanov Cc: freebsd-gnats-submit@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 wrote: > ... >>Description: > System with 'nullfs' in fstab can't boot without root's help because it c= an't exec fsck_nullfs on startup. >>How-To-Repeat: >> 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 >> >>Fix: > Simple fix - create file /sbin/fsck_nullfs: > >> more /sbin/fsck_nullfs > #!/bin/sh > exit 0 Hi Alexander, 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_* /sbin/fsck_4.2bsd /sbin/fsck_ffs /sbin/fsck_msdosfs /sbin/fsck_ufs /sbin/mount_cd9660 /sbin/mount_mfs /sbin/mount_msdosfs /sbin/mount_newnfs /sbin/mount_nfs /sbin/mount_ntfs /sbin/mount_nullfs /sbin/mount_udf /sbin/mount_unionfs 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= (8) command to determine which file systems need to be dumped. If the fif= th 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= s 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= ned and fsck(8) and quotacheck(8) will assume that the file system does no= t 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 above. Thanks, -Garrett