Subject: kern/23462: vinum vs. NetBSD device names / vinum cannot recover configuration from vinum drives on /dev/wd0i and above
To: None <gnats-bugs@gnats.netbsd.org>
From: Frank Kardel <kardel@pip.acrys.com>
List: netbsd-bugs
Date: 11/16/2003 23:32:54
>Number:         23462
>Category:       kern
>Synopsis:       vinum cannot recover configuration from vinum drives on /dev/wd0i and above
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 16 22:33:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Frank Kardel
>Release:        NetBSD 1.6ZF
>Organization:
	
>Environment:
System: NetBSD pip 1.6ZF NetBSD 1.6ZF (SYSPIP_ISDN) #0: Sat Nov 15 23:56:19 MET 2003 kardel@pip:/fs/IC35L120AVV207-0-e/src/NetBSD/netbsd/sys/arch/i386/compile/obj.i386/SYSPIP_ISDN i386
Architecture: i386
Machine: i386
>Description:
	I created 4 vinum drives on /dev/wd0{i,j,k,l} for testing purposes. after re-booting the 
	configuration could not be recovered from thoses drives (vinum: no drives found - see vinumio.c:871).
	The device name scanning code does not seem to match the NetBSD device name methodology.
	Indications are: vinumio.c:819 'slice' numbers from 1-4
			 vinumio.c:820/845 partition letters from a - h (8 hardcoded partitions instead of NetBSDs 16 on i386)

	It looks like this code still needs a few adjustments to work on i386.

>How-To-Repeat:
	configure vinum drives on partions starting at i and above. re-boot and try to get vinum to
	access these drives.

>Fix:
	Adjust code in vinumio.c to match the actual NetBSD logic.
>Release-Note:
>Audit-Trail:
>Unformatted:
 	-current of 200301115