On 2/06/10 03:11 PM, Fred Liu wrote:
Fix some typos.....
#########################################################################################################
In fact, there is no problem for MPxIO name in technology.
It only matters for storage admins to remember the name.
You are correct.
I think there is no way to give short aliases to these long tedious MPxIO name.
You are correct that we don't have aliases. However, I do not
agree that the naming is tedious. It gives you certainty about
the actual device that you are dealing with, without having
to worry about whether you've cabled it right.
And I just have only one HBA card, so I don't need multipath indeed.
For SAS and FC-attached devices, we are moving (however slowly) towards
having MPxIO on all the time.
Please don't assume that turning on MPxIO requires you to have
multiple ports and/or HBAs - for the addressing scheme at least,
it does not. Failover.... that's another matter.
The simple name -- cxtxdx will be much more easier.
That naming system is rooted in parallel scsi times. It is not
appropriate for SAS and FC environments.
Furthermore, my ultimate goal is to map the disk in MPxIO path
> to the actual physical slot
position. And If there is a broken HDD, I can easily know to
> replace which one.
BTW, the "luxadm led_blink" may not work in the commodity hardware
> and only works in Sun's proprietary disk array.
I think it is a common situation for storage admins.
**How do you replace the broken HDDs in your best practice?**
If you are running build 126 or later, then you can take advantage
of the behaviour that was added to cfgadm(1m):
$ cfgadm -lav c3 c4
Ap_Id Receptacle Occupant Condition
Information
When Type Busy Phys_Id
c3 connected configured unknown
unavailable scsi-sas n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi
c3::0,0 connected configured unknown Client
Device: /dev/dsk/c5t5000CCA00510A7CCd0s0(sd37)
unavailable disk-path n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi::0,0
c3::dsk/c3t2d0 connected configured unknown
ST3320620AS ST3320620AS
unavailable disk n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi::dsk/c3t2d0
c3::dsk/c3t3d0 connected configured unknown
ST3320620AS ST3320620AS
unavailable disk n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi::dsk/c3t3d0
c3::dsk/c3t4d0 connected configured unknown
ST3320620AS ST3320620AS
unavailable disk n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi::dsk/c3t4d0
c3::dsk/c3t6d0 connected configured unknown
ST3320620AS ST3320620AS
unavailable disk n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi::dsk/c3t6d0
c4 connected configured unknown
unavailable scsi-sas n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi
c4::5,0 connected configured unknown Client
Device: /dev/dsk/c5t50000F001BB01248d0s0(sd38)
unavailable disk-path n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi::5,0
c4::6,0 connected configured unknown Client
Device: /dev/dsk/c5t50014EE1007EE473d0s0(sd39)
unavailable disk-path n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi::6,0
c4::dsk/c4t3d0 connected configured unknown
ST3320620AS ST3320620AS
unavailable disk n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi::dsk/c4t3d0
c4::dsk/c4t7d0 connected configured unknown
ST3320620AS ST3320620AS
unavailable disk n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi::dsk/c4t7d0
While the above is a bit unwieldy to read in an email, it does
show you the following things:
(0) I have SAS and SATA disks
(1) I have MPxIO turned on
(2) the MPxIO-capable devices are listed with both their "client"
or scsi_vhci path, and their traditional cXtYdZ name
$ cfgadm -lav c3::0,0 c4::5,0 c4::6,0
Ap_Id Receptacle Occupant Condition
Information
When Type Busy Phys_Id
c3::0,0 connected configured unknown Client
Device: /dev/dsk/c5t5000CCA00510A7CCd0s0(sd37)
unavailable disk-path n
/devices/p...@0,0/pci10de,3...@a/pci1000,3...@0:scsi::0,0
c4::5,0 connected configured unknown Client
Device: /dev/dsk/c5t50000F001BB01248d0s0(sd38)
unavailable disk-path n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi::5,0
c4::6,0 connected configured unknown Client
Device: /dev/dsk/c5t50014EE1007EE473d0s0(sd39)
unavailable disk-path n
/devices/p...@ff,0/pci10de,3...@f/pci1000,3...@0:scsi::6,0
No need to use luxadm.
James C. McPherson
--
Senior Software Engineer, Solaris
Oracle
http://www.jmcp.homeunix.com/blog
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
