From nobody@FreeBSD.org  Wed Apr 21 09:08:02 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1ABFA106564A
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 21 Apr 2010 09:08:02 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 0A0608FC12
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 21 Apr 2010 09:08:02 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o3L981ua034513
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 21 Apr 2010 09:08:01 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o3L981Eq034511;
	Wed, 21 Apr 2010 09:08:01 GMT
	(envelope-from nobody)
Message-Id: <201004210908.o3L981Eq034511@www.freebsd.org>
Date: Wed, 21 Apr 2010 09:08:01 GMT
From: Alexander Yamshanov <alexander@yamshanov.ru>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Problem with nullfs in fstab on boot
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         145910
>Category:       misc
>Synopsis:       Problem with nullfs in fstab on boot
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 21 09:10:03 UTC 2010
>Closed-Date:    Thu Aug 19 21:30:30 UTC 2010
>Last-Modified:  Thu Aug 19 21:30:30 UTC 2010
>Originator:     Alexander Yamshanov
>Release:        FreeBSD 7.3-RELEASE
>Organization:
>Environment:
FreeBSD YottaByte.cis.ru 7.3-RELEASE FreeBSD 7.3-RELEASE #1: Tue Apr 20 17:06:29 NOVST 2010     sasha@:/usr/src/sys/i386/compile/YOTTABYTE  i386
>Description:
System with 'nullfs' in fstab can't boot without root's help because it can't exec fsck_nullfs on startup.
>How-To-Repeat:
> grep nullfs /etc/fstab
/export/home            /usr/home       nullfs  rw              2       2
>
>Fix:
Simple fix - create file /sbin/fsck_nullfs:

> more /sbin/fsck_nullfs
#!/bin/sh
exit 0
>

>Release-Note:
>Audit-Trail:

From: Garrett Cooper <yanefbsd@gmail.com>
To: Alexander Yamshanov <alexander@yamshanov.ru>
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
 <alexander@yamshanov.ru> 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
State-Changed-From-To: open->closed 
State-Changed-By: vwe 
State-Changed-When: Thu Aug 19 21:29:59 UTC 2010 
State-Changed-Why:  
WONTFIX: configuration problem at user side 

http://www.freebsd.org/cgi/query-pr.cgi?pr=145910 
>Unformatted:
