From: "spren.gm@gmail.com" <spren.gm@gmail.com>
To: JörnEngel <joern@logfs.org>, BjørnMork <bjorn@mork.no>,
"Nagalakshmi Nandigama" <Nagalakshmi.Nandigama@lsi.com>,
"Sreekanth Reddy" <Sreekanth.Reddy@lsi.com>,
"support@lsi.com" <support@lsi.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
"DL-MPTFusionLinux@lsi.com" <DL-MPTFusionLinux@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: mpt2sas: device_blocked question
Date: Sat, 26 Jan 2013 11:52:14 +0800 [thread overview]
Message-ID: <201301261152058902951@gmail.com> (raw)
In-Reply-To: 20130125192039.GE22141@logfs.org
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
next prev parent reply other threads:[~2013-01-26 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 21:20 [PATCH] mpt2sas: prevent double free on error path Jörn Engel
2013-01-24 7:51 ` Bjørn Mork
2013-01-24 7:51 ` Bjørn Mork
2013-01-25 17:12 ` Jörn Engel
2013-01-25 18:00 ` [PATCH v2] mpt2sas/mpt3sas: " Jörn Engel
2013-01-25 18:00 ` Jörn Engel
2013-01-25 19:20 ` [PATCH v3] " Jörn Engel
2013-01-26 3:52 ` spren.gm [this message]
2013-01-30 6:52 ` mpt2sas: device_blocked question Reddy, Sreekanth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201301261152058902951@gmail.com \
--to=spren.gm@gmail.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=JBottomley@parallels.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=Sreekanth.Reddy@lsi.com \
--cc=bjorn@mork.no \
--cc=joern@logfs.org \
--cc=linux-scsi@vger.kernel.org \
--cc=support@lsi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.