From: vaughan <vaughan.cao@oracle.com>
To: Hannes Reinecke <hare@suse.de>, Steffen Maier <maier@linux.vnet.ibm.com>
Cc: JBottomley@parallels.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: special sense code asc,ascq=04h,0Ch abort scsi scan in the middle
Date: Mon, 21 Oct 2013 14:07:06 +0800 [thread overview]
Message-ID: <5264C48A.80900@oracle.com> (raw)
In-Reply-To: <525E37CA.2000605@suse.de>
On 10/16/2013 02:52 PM, Hannes Reinecke wrote:
> But seeing that this approach raises quite some issues I've attached a
> different patch. Vaughan, could you test with that, too? Should be
> functionally equivalent to the previous one. Cheers, Hannes
Hi Hannes,
We only tested the later patch which returns _TARGET_PRESENT after
parsing sense, it works as expected.
About the cause of this issue, admin said he is configuring a
active-active cluster mode storage. Each node has it own LUN pool and a
set of rule to control which node can access the pool.
LUN7 is owned and can only be able to manipulated by the other node, but
can be seen by this node for a misconfig. So it presents itself in
REPORT_LUN but return NOT_READY when accessed through this node.
Do you still regard this as a misbehave in response to INQUIRY?
Thanks,
Vaughan
next prev parent reply other threads:[~2013-10-21 6:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 17:23 PROBLEM: special sense code asc,ascq=04h,0Ch abort scsi scan in the middle Vaughan Cao
2013-10-14 11:13 ` Hannes Reinecke
2013-10-14 12:51 ` Steffen Maier
2013-10-14 13:18 ` Hannes Reinecke
2013-10-14 13:32 ` Hannes Reinecke
2013-10-14 15:24 ` Steffen Maier
2013-10-16 6:52 ` Hannes Reinecke
2013-10-16 7:26 ` vaughan
2013-10-21 6:07 ` vaughan [this message]
2013-10-22 17:05 ` Hannes Reinecke
2013-12-18 13:51 ` Vaughan Cao
2014-02-19 8:29 ` vaughan
2013-10-14 15:18 ` Vaughan Cao
2013-10-15 3:32 ` vaughan
2013-10-15 5:51 ` Hannes Reinecke
2013-10-15 11:46 ` Vaughan Cao
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=5264C48A.80900@oracle.com \
--to=vaughan.cao@oracle.com \
--cc=JBottomley@parallels.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.vnet.ibm.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 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).