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.
'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.
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.
locadmin@bigdawg2:~# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c10t2d0<DEFAULT cyl 9965 alt 2 hd 224 sec 56>
/pci@0,0/pci8086,340a@3/pci1000,72@0/iport@4/disk@p2,0
1. c13t5000CCA222DF92A0d0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340a@3/pci1000,72@0/iport@10/disk@w5000cca222df92a0,0
2. c14t5000CCA222DF8FBEd0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340e@7/pci1000,3020@0/iport@1/disk@w5000cca222df8fbe,0
3. c15t5000CCA222E006B6d0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340a@3/pci1000,72@0/iport@8/disk@w5000cca222e006b6,0
4. c16t5000CCA222DDD7BAd0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340c@5/pci1000,3020@0/iport@2/disk@w5000cca222ddd7ba,0
5. c17t5000CCA222DF3CECd0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340e@7/pci1000,3020@0/iport@20/disk@w5000cca222df3cec,0
6. c18t5000CCA222DEAFE6d0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340e@7/pci1000,3020@0/iport@2/disk@w5000cca222deafe6,0
7. c19t5000CCA222E0A3DEd0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340e@7/pci1000,3020@0/iport@4/disk@w5000cca222e0a3de,0
8. c20t5000CCA222E046B7d0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340e@7/pci1000,3020@0/iport@8/disk@w5000cca222e046b7,0
9. c21t5000CCA222E0533Fd0<DEFAULT cyl 60798 alt 2 hd 255 sec 252>
/pci@0,0/pci8086,340a@3/pci1000,72@0/iport@20/disk@w5000cca222e0533f,0
So now I'm more baffled than I started. Any other suggestions will be
gratefully accepted...
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.
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
