bin/134250: [rc.d] mountlate: bogus error message when using nested
late mounts
Dmitry Marakasov
amdmi3 at FreeBSD.org
Wed May 6 00:10:04 UTC 2009
>Number: 134250
>Category: bin
>Synopsis: [rc.d] mountlate: bogus error message when using nested late mounts
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed May 06 00:10:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Dmitry Marakasov
>Release: FreeBSD 8.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD hades.panopticon 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Apr 30 06:41:20 MSD 2009 root at hades.panopticon:/async/obj/usr/src/sys/HADES i386
>Description:
On some configs it's possible that bogus error from mount is displayed during boot.
The bug shows when there are nested late mounts, i.e.
/dev/ad8d /mnt ufs rw,late 0 0
/dev/ad8e /mnt/somedir ufs rw,late 0 0
Here's what mount -d -a -l shows in this case:
# mount -d -a -l
mount -t ufs -o rw -o noatime -o update /dev/ad8a /
mount -t ufs -o rw /dev/ad8d /mnt
mount: /mnt/somedir: No such file or directory
True, as /mnt/somedir does not exists unless /dev/ad8d is mounted.
That mount -d -a -l is called from /etc/rc.d/mountlate:
latefs="`/sbin/mount -d -a -l | grep -v ' /$'`"
thus that error gets into boot output - it confused me badly, though it turned out to be harmless.
>How-To-Repeat:
>Fix:
Obvious fix is:
- latefs="`/sbin/mount -d -a -l | grep -v ' /$'`"
+ latefs="`/sbin/mount -d -a -l 2>&1 | grep -v ' /$'`"
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list