On 11/01/12 04:54 AM, Ray Van Dolson wrote:
I am trying to find a generic way to identify which disk is impacted
based on the following information:
Jan 10 19:15:13 dev-zfs5 scsi: [ID 365881 kern.info]
/pci@0,0/pci8086,3410@9/pci15d9,400@0 (mpt_sas0):
Jan 10 19:15:13 dev-zfs5 Log info 0x31140000 received for target 20.
Jan 10 19:15:13 dev-zfs5 scsi_status=0x0, ioc_status=0x8048,
scsi_state=0xc
This is on a Nexenta 3.1.0 system (Community Edition) with SATA disks
and an LSI controller which presents as multipath.
As such, we have the long hairy multipath names.
<obPedant>
You've got WWID-based names, which are subtly different.
</obPedant>
I am trying to figure out how to conver "Target 20" to one of the
device names. Is it sd20? I'm not sure that it is...
It can be, but it's not guaranteed to be.
Perusing other posts, I came across a method via mdb -k plus ::prtconv
-v. I'm thinking it may be this disk:
ffffff071c44c308 scsiclass,00, instance #20 (driver name: sd)
Driver properties at ffffff071ca897e0:
name='inquiry-serial-no' type=string items=1
value='3QK0B7MF'
name='lba-access-ok' type=any items=0 dev=(292,1280)
name='pm-components' type=string items=3
value='NAME=spindle-motor' + '0=off' + '1=on'
name='pm-hardware-state' type=string items=1
value='needs-suspend-resume'
name='ddi-failfast-supported' type=any items=0
name='ddi-kernel-ioctl' type=any items=0
name='fm-ereport-capable' type=any items=0
Hardware properties at ffffff07225456e0:
name='devid' type=string items=1
value='id1,sd@n5000c500026e592b'
If you were running S11 FCS I'd suggest looking at the rest of the
elements in the output from prtconf -v. This should include info
such as "Paths from multipath bus adapters" and the devlinks for
the minor nodes, such as the s2 link.
# iostat -En | grep -i 592b
c0t5000C500026E592Bd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
However, there are no errors reported on this drive (yes there are
other drives showing errors (sd15 in specific), but don't see how they
correspond with "Target 20").
There are more lines reported for each device in iostat -En output
than what you've listed there. Here's an example from my system:
$ iostat -En c5t50024E90037AF38Cd0
c5t50024E90037AF38Cd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: SAMSUNG HD103SJ Revision: 0001 Serial No:
Size: 1000.20GB <1000204886016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 269 Predictive Failure Analysis: 0
Please note that merely seeing mpt_sas or mpt log info reported
in syslog does not necessarily mean that that device has had an
error. The "error" logged might be nothing that the SCSA framework
is interested in (which I think is the case for what you mention
above), or it could be, in which case you'd see something like this:
Jan 2 09:24:57 blinder scsi: [ID 107833 kern.warning] WARNING:
/pci@0,0/pci-ide@4/ide@0/sd@0,0 (sd13):
(and then other output too).
James C. McPherson
--
Oracle
http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
