Date: Tue, 17 Oct 2000 03:44:55 -0700 (PDT) From: opentrax@email.com To: freebsd-gnats-submit@FreeBSD.org Subject: docs/22043: fstab cache annoyance Message-ID: <20001017104455.16A4F37B479@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 22043 >Category: docs >Synopsis: fstab cache annoyance >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 17 03:50:01 PDT 2000 >Closed-Date: >Last-Modified: >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: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001017104455.16A4F37B479>