Hi,
Was curious if anyone had been running into timeouts with IBM LTO-5 drives in heavily utilized environments with QLOGIC 2562-CK (8GBPS) HBAs?
Never saw this in smaller environments with MPX <= 3 but now with MPX >= 6 some drives seem to be timing out and going into a “hung” state.
Was curious if anyone ever ran into this issue before?
Power cycling the drive (reseating it) fixes it and then it’s fine again as a workaround but not a fix, thoughts?
F/W on the IBM LTO-5 drives is BBN2 (latest from Oracle)
F/W on the HBA’s is 3.00 (latest from QLogic)
When the problem occurs (these errors spew continuously) until the drive is reseated (rebooting the robot does not clear out the errors)
st 3:0:0:0: timing out command, waited 7s
qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e08 2002.
st 3:0:0:0: timing out command, waited 7s
qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e0a 2002.
st 3:0:0:0: timing out command, waited 7s
qla2xxx 0000:0d:00.0: scsi(0:0:0): Abort command issued -- 1 1820 2002.
qla2xxx 0000:0d:00.0: scsi(0:0:0): Abort command issued -- 1 1821 2002.
st 0:0:0:0: timing out command, waited 900s
st0: Error 6080000 (sugg. bt 0x0, driver bt 0x6, host bt 0x8).
st 0:0:0:0: timing out command, waited 180s
qla2xxx 0000:0d:00.0: scsi(0:0:0): Abort command issued -- 1 1823 2002.
st 0:0:0:0: timing out command, waited 60s
qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e18 2002.
st 3:0:0:0: timing out command, waited 7s
qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e1a 2002.
st 3:0:0:0: timing out command, waited 7s
Justin.