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.
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...
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'
# 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").
Can anyone help me out?
Thanks,
Ray
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
