NetBSD Problem Report #49135

From www@NetBSD.org  Thu Aug 21 13:50:38 2014
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 2CA29AE75C
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 21 Aug 2014 13:50:38 +0000 (UTC)
Message-Id: <20140821135036.9C485AE75C@mollari.NetBSD.org>
Date: Thu, 21 Aug 2014 13:50:32 +0000 (UTC)
From: jdbaker@mylinuxisp.com
Reply-To: jdbaker@consolidated.net
To: gnats-bugs@NetBSD.org
Subject: wedge support thwarts read/write update of root filesystem with traditional device path in fstab
X-Send-Pr-Version: www-1.0

>Number:         49135
>Notify-List:    jdbaker@consolidated.net
>Category:       kern
>Synopsis:       wedge support thwarts read/write update of root filesystem with traditional device path in fstab
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 21 13:55:00 +0000 2014
>Last-Modified:  Tue Jan 29 06:31:38 +0000 2019
>Originator:     John D. Baker
>Release:        NetBSD/i386-7.99.1 after 18-Aug-2014 06:32 UTC
>Organization:
>Environment:
NetBSD brenowin.reltuk.net 7.99.1 NetBSD 7.99.1 (RELTUK) #4: Thu Aug 21 07:31:45 CDT 2014  sysop@kepler.clamp.net:/d0/nbsd/current/obj/i386/sys/arch/i386/compile/RELTUK i386

>Description:
On a system with traditional device paths in "/etc/fstab":

/dev/ld0a      /       ffs     rw,log   1 1
/dev/ld0b      none    swap    sw,dp    0 0
/dev/ld0e      /tmp    ffs     rw,log,nosuid,nodev      1 2
/dev/ld0f      /var    ffs     rw,log,nosuid    1 2
/dev/ld0g      /usr    ffs     rw,log,nodev     1 2
#/dev/ld0h      /home   ffs     rw,log,nosuid,nodev      1 2

the enabling of MBR/disklabel wedge support caused "/etc/rc.d/root" to
fail updating the "root_device" to read/write with the error:

  specified device does not match mounted device

although "swap[12]" and "mountall" proceed to mount the devices as
before.  The output of 'mount' shows "root_device" for "/" and the
traditional device paths for the rest.

Looking back through 'dmesg' showed various "dkN" devices being
assigned, so that was a clue.
>How-To-Repeat:
On a system with tradtional "/dev/xxNp" device paths in "/etc/fstab"
boot a kernel built with MBR/DISKLABEL wedge support enabled.

(Perhaps this only happens on systems with hardware RAID or other
"ld" disk devices?)
>Fix:
For the immediate case of updating "/" to read/write, find the "dkN"
device associated with the traditional device, or use "NAME=...":

  mount -t ffs -u /dev/dk0

or (in the case of un-named/fictitious label)

  mount -t ffs -u NAME=ld0a

after which one may edit "/etc/fstab" accordingly.  For the no-name
fictitious label case:

# wedge support is now mandatory, use NAME=<device> for no-name disklabel
NAME=ld0a       /       ffs     rw,log   1 1
NAME=ld0b       none    swap    sw,dp    0 0
NAME=ld0e       /tmp    ffs     rw,log,nosuid,nodev      1 2
NAME=ld0f       /var    ffs     rw,log,nosuid    1 2
NAME=ld0g       /usr    ffs     rw,log,nodev     1 2
#NAME=ld0h      /home   ffs     rw,log,nosuid,nodev      1 2

>Release-Note:

>Audit-Trail:

>Unformatted:

Home	PR Database Search