Hi,
I noticed that fmdump -ev shows io.scsi errors an each of my snv134 boxes, like
this:
Okt 08 10:51:09.7654 ereport.io.scsi.cmd.disk.recovered 0x9244675396301401
Okt 08 10:51:09.7654 ereport.io.scsi.cmd.disk.recovered 0x9244675396301401
Okt 08 10:51:09.7654 ereport.io.scsi.cmd.disk.recovered 0x9244675396301401
Okt 08 10:51:09.7654 ereport.io.scsi.cmd.disk.recovered 0x9244675396301401
Okt 08 10:51:09.7654 ereport.io.scsi.cmd.disk.recovered 0x9244675396301401
Okt 08 10:51:09.7654 ereport.io.scsi.cmd.disk.recovered 0x9244675396301401
Okt 08 10:51:09.7651 ereport.io.scsi.cmd.disk.tran 0x924466ea94401001
Okt 08 10:51:09.7651 ereport.io.scsi.cmd.disk.tran 0x924466e1fd501401
Okt 08 10:51:09.7651 ereport.io.scsi.cmd.disk.recovered 0x924466e1fd501401
Okt 08 10:51:09.7651 ereport.io.scsi.cmd.disk.recovered 0x924466e1fd501401
Okt 08 10:51:09.7651 ereport.io.scsi.cmd.disk.tran 0x924466e010601401
Okt 08 10:51:09.7651 ereport.io.scsi.cmd.disk.tran 0x924466dd58801401
Okt 08 10:51:12.8892 ereport.io.scsi.cmd.disk.tran 0x92500a4ff4800c01
Okt 08 10:51:12.8893 ereport.io.scsi.cmd.disk.tran 0x92500a5382800c01
Okt 08 10:51:12.8895 ereport.io.scsi.cmd.disk.tran 0x92500a86f5000801
Okt 08 10:51:12.8895 ereport.io.scsi.cmd.disk.tran 0x92500a8b5af00801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.tran 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
Okt 08 10:51:12.8896 ereport.io.scsi.cmd.disk.recovered 0x92500a9c0ca01801
On this particular box, the LUN in question is connected through a FC switch
and the HBA is a QLE2460.
I checked which device raised these errors and it's always the same, so I
suspect that there's something going on with the FC connection, although
there're no messages in the syslog.
fmdump -eV shows these issues:
Okt 08 2010 10:51:12.889601331 ereport.io.scsi.cmd.disk.tran
nvlist version: 0
class = ereport.io.scsi.cmd.disk.tran
ena = 0x92500a9c0ca01801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/p...@0,0/pci8086,3...@9/pci1077,1...@0/f...@0,0/d...@w2100001378ac026e,0
(end detector)
driver-assessment = retry
op-code = 0x8a
cdb = 0x8a 0x0 0x0 0x0 0x0 0x3 0x1a 0x49 0xc9 0xee 0x0 0x0 0x1 0x0 0x0
0x0
pkt-reason = 0x3
pkt-state = 0x0
pkt-stats = 0x20
__ttl = 0x1
__tod = 0x4caedb80 0x35063d33
Okt 08 2010 10:51:12.889604904 ereport.io.scsi.cmd.disk.recovered
nvlist version: 0
class = ereport.io.scsi.cmd.disk.recovered
ena = 0x92500a9c0ca01801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/p...@0,0/pci8086,3...@9/pci1077,1...@0/f...@0,0/d...@w2100001378ac026e,0
devid = id1,s...@n2034001378ac026e
(end detector)
driver-assessment = recovered
op-code = 0x8a
cdb = 0x8a 0x0 0x0 0x0 0x0 0x3 0x1a 0x49 0x7e 0xa9 0x0 0x0 0x1 0x0 0x0
0x0
pkt-reason = 0x0
pkt-state = 0x1f
pkt-stats = 0x0
__ttl = 0x1
__tod = 0x4caedb80 0x35064b28
Does anybody know what these errors mean?
Thanks,
budy
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
