On 2/27/11 5:15 AM, "James C. McPherson" <j...@opensolaris.org> wrote:
>On 27/02/11 05:24 PM, Dave Pooser wrote: >>On 2/26/11 7:43 PM, "Bill Sommerfeld"<sommerf...@hamachi.org> wrote: >> >>>On your system, c12 is the mpxio virtual controller; any disk which is >>>potentially multipath-able (and that includes the SAS drives) will >>>appear as a child of the virtual controller (rather than appear as the >>>child of two or more different physical controllers). >> >>Hmm... That makes sense, except that my drives are all SATA because I'm >>cheap^H^H^H fiscally conservative. :^) > >They're attached to a SAS hba, which is doing translations for them >using SATL - SAS to ATA Translation Layer. Yeah, but they're still not multipathable, are they? >>'stmsboot -L' displayed no mappings, > >this is because mpt_sas(7d) controllers - which you have - are using >MPxIO by default. Running stmsboot -L will only show mappings if you've >enabled or disabled MPxIO.... > >> but I went ahead and tried stmsboot >>-d to disable multipathing; > >... and now you have disabled MPxIO, stmsboot -L should show mappings. Nope: locadmin@bigdawg2:~# stmsboot -L stmsboot: MPXIO disabled >>after reboot instead of seeing nine disks on a >>single controller I now see ten different controllers (in a machine that >>has four PCI controllers and one motherboard controller): > >This is a side effect of how your expanders are configured to operate >on your motherboard. But there shouldn't be any expanders in the system-- the front backplane has six SFF-8087 ports to control 24 drives, and the rear backplane has three more SFF-8087 ports to control 12 more drives. Each of those ports is connected directly to an SFF-8087 port on an LSI 9211-8i controller, except that the ninth port is connected to the integrated LSI 2008 controller on the motherboard. >If you're lucky, your expanders and the enclosure that they're >configured into will show up with one or more SES targets. If >that's the case, you might be able to see bay numbers with the >fmtopo command - when you run it as root: > ># /usr/lib/fm/fmd/fmtopo -V > >If this doesn't work for you, then you'll have to resort to the >tried and tested use of dd to /dev/null for each disk, and see >which lights blink. 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. Probably my next step is going to be to take a look with Nexenta Core or FreeBSD (or maybe SolEx11 for a temporary eval) and see if either of those gives me a saner view, but other suggestions would be appreciated. -- Dave Pooser, ACSA Manager of Information Services Alford Media http://www.alfordmedia.com <http://www.alfordmedia.com/> _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
