From: Bart Van Assche <bvanassche@acm.org>
To: Brian Bunker <brian@purestorage.com>, linux-scsi@vger.kernel.org
Cc: Martin Wilck <mwilck@suse.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Subject: Re: The PQ=1 saga
Date: Fri, 27 Jan 2023 12:43:12 -0800 [thread overview]
Message-ID: <65e11f62-0109-ee6f-0cd0-56ae30dd1208@acm.org> (raw)
In-Reply-To: <6A8AA317-32B0-48F4-82DC-82B65A221A9F@purestorage.com>
On 1/27/23 11:57, Brian Bunker wrote:
> So the question becomes how should initial scan work when a LUN has a PQ=1 set.
> It is a valid, by spec with ALUA state unavailable but doesn’t seem to be
> handled. Why allow an sg device but not an sd one on initial scan in this case? There
> are probably many ways to fix this. I think the simplest is to allow sd device creation
> on LUNs were PQ=1, and only restrict PQ=3. I am not sure the side effect of this on other
> targets. The other approach which will no longer work after the revert is to trigger a
> rescan from the target. This is sub-optimal since it is disruptive. Any approach involving
> the ALUA device handler will not help since there is no device to transition if it is
> discovered with PQ=1.
When Mike Christie and I looked into the ALUA unavailable state many
years ago we concluded that using this state is so troublesome that it's
better not to use this state. How about using active/optimized and
active/non-optimized instead?
Thanks,
Bart.
next prev parent reply other threads:[~2023-01-27 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 0:01 The PQ=1 saga Martin K. Petersen
2023-01-25 1:02 ` Brian Bunker
2023-01-25 4:04 ` Martin K. Petersen
2023-01-25 19:56 ` Brian Bunker
2023-01-25 20:36 ` Bart Van Assche
2023-01-25 1:41 ` Bart Van Assche
2023-01-25 8:33 ` Martin Wilck
2023-01-26 9:01 ` Hannes Reinecke
2023-01-27 19:57 ` Brian Bunker
2023-01-27 20:43 ` Bart Van Assche [this message]
2023-01-27 21:33 ` Brian Bunker
2023-01-30 13:35 ` Hannes Reinecke
2023-01-31 21:00 ` Brian Bunker
2025-11-20 16:46 ` Brian Bunker
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=65e11f62-0109-ee6f-0cd0-56ae30dd1208@acm.org \
--to=bvanassche@acm.org \
--cc=brian@purestorage.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mwilck@suse.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