From: Christoph Hellwig <hch@infradead.org>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: haowenchao@huawei.com, open-iscsi <open-iscsi@googlegroups.com>,
linfeilong@huawei.com, liuzhiqiang26@huawei.com,
jejb@linux.ibm.com, martin.petersen@oracle.com,
michael.christie@oracle.com, Chris Leech <cleech@redhat.com>,
Lee Duncan <lduncan@suse.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Antw: [EXT] Re: [PATCH 0/2] scsi:donot skip lun if inquiry returns PQ=1 for all hosts
Date: Thu, 15 Dec 2022 23:11:13 -0800 [thread overview]
Message-ID: <Y5waEc0iqfGkkN7f@infradead.org> (raw)
In-Reply-To: <639AD5C0020000A100050749@gwsmtp.uni-regensburg.de>
On Thu, Dec 15, 2022 at 09:07:28AM +0100, Ulrich Windl wrote:
> Actusally I have no idea, but as a user of FC SAN systems I can remember a case when a storage system had to present a dummy LUN0 to enable hosts to find other LUNs (while LUN0 was never actually used). Maybe the client code was imperfect, I don't know.
Ignoring some of the well known LU bits that never really became
practically relevant, lun0 is needed to use the REPORT_LUNS command
to scane for the other logical units. But unless the PQ says it
actually is a valid logic unit, we never add a sdev for it.
next prev parent reply other threads:[~2022-12-16 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 7:08 [PATCH 0/2] scsi:donot skip lun if inquiry returns PQ=1 for all hosts Wenchao Hao
2022-12-14 7:08 ` [PATCH 1/2] scsi:core:Add sysfs interface to control if skip lun with PQ=1 Wenchao Hao
2022-12-18 21:37 ` Mike Christie
2022-12-28 8:46 ` Wenchao Hao
2022-12-14 7:08 ` [PATCH 2/2] scsi:iscsi_tcp:Do not skip lun inquiry returns PQ=1 Wenchao Hao
2022-12-15 7:06 ` [PATCH 0/2] scsi:donot skip lun if inquiry returns PQ=1 for all hosts Christoph Hellwig
2022-12-15 8:07 ` Antw: [EXT] " Ulrich Windl
2022-12-16 7:11 ` Christoph Hellwig [this message]
2022-12-15 9:09 ` Wenchao Hao
2022-12-16 7:12 ` Christoph Hellwig
2022-12-16 11:41 ` Wenchao Hao
2022-12-23 15:54 ` Christoph Hellwig
2022-12-28 9:35 ` Wenchao Hao
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=Y5waEc0iqfGkkN7f@infradead.org \
--to=hch@infradead.org \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=cleech@redhat.com \
--cc=haowenchao@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=lduncan@suse.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=open-iscsi@googlegroups.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