>Number:         14116
>Category:       bin
>Synopsis:       mlxctl claims ld1 isn't attached to mlx0.  It is.
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 01 08:34:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Ben Harris
>Release:        20010827 with fix from bin/14086 applied
>Organization:
University of Cambridge Computing Service
>Environment:
NetBSD 1.5X (GENERIC) #0: Tue Aug 28 06:33:30 PDT 2001
    chs@pc:/usr/chs/netbsd/obj/usr/chs/netbsd/src/sys/arch/i386/compile/GENERIC

mlx0 at pci0 dev 12 function 0: Mylex RAID (v3 interface)
mlx0: interrupting at irq 11
mlx0: DAC960P/PD, 2 channels, firmware 3.52-0-02, 32MB RAM
ld0 at mlx0 unit 0: RAID5, online
ld0: 52290 MB, 6666 cyl, 255 head, 63 sec, 512 bytes/sect x 107089920 sectors
ld1 at mlx0 unit 1: JBOD, online
ld1: 8715 MB, 4426 cyl, 64 head, 63 sec, 512 bytes/sect x 17848320 sectors

>Description:
As above, the system finds ld1, and is able to use it successfully, but
mlxctl says:

balrog# ./mlxctl -v status ld0
ld0: online
balrog# ./mlxctl -v status ld1
mlxctl: ld1 is not attached to mlx0

>How-To-Repeat:
See above.  I've not tried it on another system.

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: