From nobody@FreeBSD.ORG  Tue Oct 17 03:44:55 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 16A4F37B479; Tue, 17 Oct 2000 03:44:55 -0700 (PDT)
Message-Id: <20001017104455.16A4F37B479@hub.freebsd.org>
Date: Tue, 17 Oct 2000 03:44:55 -0700 (PDT)
From: opentrax@email.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: fstab cache annoyance
X-Send-Pr-Version: www-1.0

>Number:         22043
>Category:       docs
>Synopsis:       fstab cache annoyance
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 17 03:50:01 PDT 2000
>Closed-Date:    Sun Nov 12 10:23:17 PST 2000
>Last-Modified:  Sun Nov 12 10:25:59 PST 2000
>Originator:     jesse monroy
>Release:        3.4
>Organization:
digital marshalls
>Environment:
FreeBSD biggie.mozie.org 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Aug 28 08:29:03 PDT 2000 jessem@biggie.mozie.org:/usr/src/sys/compile/JEN2 i386

>Description:
For utilities that rely on fstab (mount, fsck, ...),
the lookup in fstab(5) fails until the table is
re-read; usually a re-read via reboot.
This happens when a new entry is added to fstab(5)
and you immediately try to use it.

>How-To-Repeat:
Boot the system with a new piece of hardware(ie. CROM drive)
Add an entry to fstab, then try to reference it in
a mount command.

example:
# mount /cdrom3

>Fix:
Workaround: add to fstab and reboot system.

>Release-Note:
>Audit-Trail:

From: Ben Smithurst <ben@FreeBSD.org>
To: opentrax@email.com
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: docs/22043: fstab cache annoyance
Date: Sat, 11 Nov 2000 19:54:31 +0000

 opentrax@email.com wrote:
 
 > For utilities that rely on fstab (mount, fsck, ...),
 > the lookup in fstab(5) fails until the table is
 > re-read; usually a re-read via reboot.
 
 Utilities that read fstab read it themselves, there is no cache in the
 way you imply.  I'm not sure what the problem is.
 
 -- 
 Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D
 
State-Changed-From-To: open->closed 
State-Changed-By: billf 
State-Changed-When: Sun Nov 12 10:23:17 PST 2000 
State-Changed-Why:  
There is no such thing as a fstab cache, this file is read 
every time, as experienced by thousands of sysadmins daily. 

For more information please view the source for the getfsent() 
family of functions. 

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