> Date: Mon, 28 Feb 2011 22:02:37 +0100 (CET) > From: Roy Sigurd Karlsbakk <r...@karlsbakk.net> > > > > 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 > > lsiutil can help. The question is whether the physical labels or > > silkscreen match the "slot" as reported by lsiutil. > > Last I checked, it didn't help much. IMHO we need a driver that can > display the drives in the order they're plugged in. Like Windoze. > Like Linux. Like FreeBSD. I really don't understand what should be > so hard to do it like the others. As one said "I don't have their > sources", both Linux and FreeBSD are OSS software, so the source > should be ready quite easuly.
OK, so I'm a little behind on this, but... Yes, it is nice to know controller order - well, maybe. That assume the LSI hasn't decided to remap targets because you've moved drives around - the 1068/78 supported target persistence, but the LSI2008 doesn't. Nothing's guaranteed. The SES driver is, I presume, a fairly generic driver for knowing about enclosures. sd(7) on the other hand doesn't really know crap, other than "this is the DDI path to what I want to talk to" from which it can infer a target, but it doesn't know that that target means anything, and in my humble experience (having a whole pile of SMC hardware on LSI controllers), it really has NFC - and it doesn't need to, since it's just the bit controlling the drive - what does it care what slot it's in? You can use lsiutil advanced commands to query the expander chip and get the topology, but that's a PITA. The best way to deal with it IMHO - assuming you're serious about the need and willing to pay a small fee - is to go to www.santools.com and buy a license for smartmon-ux (no relation to smartmontools). One command, and it will generate a complete topology of your system, mapping drive serial number to WWN to DDI path to enclosure to slot in one nice big file. (It can also do lots of other nifty things but that's not the point. However, being able to map /dev/dsk/cXtYdZsA -> encBslotC and toggle LEDs is rather important when you've got a few hundred drives strung to a couple boxes. And at least for SMC 847s, the slots do match the silkscreen (or the schema in the manual). -bacon (it's amazing how many drives you can string off a box, with a little effort...) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
