Skip to contentSkip to conversation

device_blocked with mpt2sas

DISCUSSION [email protected] 1 participant 1 message Jan 23, 2013 SCSI

lore
Share & tools
lore
#0 lore raw

Hi,
we encounter a problem that a disk is blocked forever with mpt2sas, the key log is:

mpt2sas0: TEST_UNIT_READY: handle(0x000a), lun(0)
mpt2sas0: TEST_UNIT_READY: handle(0x000a), lun(0)
mpt2sas0: Spinning up disk.... handle(0x000a), lun(0)
mpt2sas0: TEST_UNIT_READY: handle(0x000a), lun(0)
mpt2sas0: Spinning up disk.... handle(0x000a), lun(0)
mpt2sas0: TEST_UNIT_READY: handle(0x000a), lun(0)
mpt2sas0: Spinning up disk.... handle(0x000a), lun(0) sd 2:0:1:0: device_blocked, handle(0x000a)

looking into the driver code, it seems that the device is blocked by function
_scsih_block_io_to_children_attached_directly() in mpt2sas/mpt2sas_scsih.c
with reason_code == MPI2_EVENT_SAS_TOPO_RC_DELAY_NOT_RESPONDING,
my question is what this reason_code mean? when should it be returned? and any way to handle it?

Best Regards,
spren
2013-01-23