Hi Spren, Reason code MPI2_EVENT_SAS_TOPO_RC_DELAY_NOT_RESPONDING mean that "A target device has stopped responding or is missing but the ReportDeviceMissingDelay timer has not expired for this device". Can you please send me the some more information i.e. 1. For which operation/TestCase this issue has occurred? 2. Which Driver & Firmware version you are using? 3. Can you also please send me the complete log. Thanks, Sreekanth. -----Original Message----- From: spren.gm@xxxxxxxxx [mailto:spren.gm@xxxxxxxxx] Sent: Saturday, January 26, 2013 9:22 AM To: JörnEngel; BjørnMork; Nandigama, Nagalakshmi; Reddy, Sreekanth; Support; James E.J. Bottomley; DL-MPT Fusion Linux Cc: linux-scsi@xxxxxxxxxxxxxxx Subject: mpt2sas: device_blocked question Hi, we encounter a problem that a disk is blocked forever, 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, what does this reason_code mean please? when should it be returned? and any way to handle it? Best Regards, spren 2013-01-26 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
