From: Bart Van Assche <bvanassche@acm.org>
To: "Moger, Babu" <Babu.Moger@netapp.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] scsi_dh_alua: Re-enable STPG for unavailable ports
Date: Fri, 22 Jun 2012 18:50:20 +0000 [thread overview]
Message-ID: <4FE4BE6C.1080608@acm.org> (raw)
In-Reply-To: <77471C95FAFD844C8CA02DD4F4C5FE2B07E504FD@SACEXCMBX02-PRD.hq.netapp.com>
On 06/22/12 17:52, Moger, Babu wrote:
> One concern, the spec also says..
> ==============================
> The unavailable target port asymmetric access state is
> intended for situations when the target port accessibility to a logical unit may be severely restricted due to SCSI
> target device limitations (e.g., hardware errors). Therefore it may not be possible to transition from this state to
> either the active/optimized, active/non-optimized or standby states.
> =====================================================
>
> What happens if we cannot transition to active/optimized, active/non-optimized or standby states.
> Are we going to loop forever? From kernel side it looks ok. We are going mark the path as failed.
> It depends on what the path checker from multipath is going to do. Do you have any idea about it?
Good question. I'm not a multipath expert, but as far as I understand
the multipath user space software if activating a path fails after some
delay multipathd tries again to find a usable I/O path.
Bart.
next prev parent reply other threads:[~2012-06-22 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 8:49 [PATCH] scsi_dh_alua: Re-enable STPG for unavailable ports Bart Van Assche
2012-06-22 17:52 ` Moger, Babu
2012-06-22 18:50 ` Bart Van Assche [this message]
2012-06-22 20:05 ` Moger, Babu
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=4FE4BE6C.1080608@acm.org \
--to=bvanassche@acm.org \
--cc=Babu.Moger@netapp.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
/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