On 28/02/11 03:18 AM, Roy Sigurd Karlsbakk wrote:
I can live with that-- but I really want to know what (real, not
virtual) controllers disks are connected to; I want to build 3 8-disk
RAIDz2 vdevs now (with room for a fourth for expansion later) and I
really want to make sure each of those vdevs has fewer than three
disks per controller so a single controller failure can degrade my
vdevs but not kill them.
I cannot but agree. On Linux and Windoze (haven't tested FreeBSD),
drives connected to an LSI9211 show up in the correct order, but not on
OI/osol/S11ex (IIRC), and fmtopo doesn't always show a mapping between
device name and slot, since that relies on the SES hardware being
properly supported. The answer I've got for this issue is, it's not an
issue, since it's that way by design etc. This doesn't make sense when
Linux/Windows show the drives in the correct order. IMHO this looks
more like a design flaw in the driver code
In Solaris-land we have different design requirements for drivers
when compared with Linux and Windows. As to what Linux and Windows
do inside their drivers, I cannot say - I don't have their source.
It is possible that since Linux and Windows are fairly closely tied
to the PC architecture, that perhaps they do some bios calls to
try to figure out "correct order" mappings.
James C. McPherson
--
Oracle
http://www.jmcp.homeunix.com/blog
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
