* device_blocked with mpt2sas
@ 2013-01-23 8:19 spren.gm
0 siblings, 0 replies; only message in thread
From: spren.gm @ 2013-01-23 8:19 UTC (permalink / raw)
To: linux-scsi
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-01-23 8:19 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-23 8:19 device_blocked with mpt2sas spren.gm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).