From: Takahiro Yasui <tyasui@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_devinfo: update Hitachi entries
Date: Fri, 26 Jun 2009 20:18:54 -0400 [thread overview]
Message-ID: <4A45656E.4050903@redhat.com> (raw)
In-Reply-To: <4A26A787.6020903@redhat.com>
On 06/03/09 12:40, Takahiro Yasui wrote:
> http://marc.info/?l=linux-scsi&m=114366299120761&w=2
>> - Blacklist flags are not used to do special handling if needed.
>> - If the device does NOT support the REPORT_LUNS scan, we won't
>> see any LUN at all, as we don't even look for LUN 1 then.
>
> In kernel 2.6.16, sequential_lun_scan() had a argument, lun0_res,
> and lun >=1 was not recognized when lun0 was not attached. Therefore,
> it seems that BLIST_ATTACH_PQ3 was necessary to pretend lun0 exists.
>
> But if those two are the only reason to be solved, I don't think
> BLIST_ATTACH_PQ3 is necessary for storages which can handle REPORT_LUNS.
>
> As you mentioned, leaving BLIST_ATTACH_PQ3 in the flag does not change
> the original behaviour, but I hope the BLIST_ATTACH_PQ3 flag is removed
> from OPEN-E so that lun0 is not installed when a storage returns PQ3 as
> other storages.
I will evaluate BLIST_ATTACH_PQ3 flags on our storages, and post
the result here. Please give me some time.
Thanks,
Taka
prev parent reply other threads:[~2009-06-27 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 16:46 [PATCH] scsi_devinfo: update Hitachi entries Takahiro Yasui
2009-06-01 16:54 ` James Bottomley
2009-06-01 17:38 ` Takahiro Yasui
2009-06-01 20:06 ` James Bottomley
2009-06-03 16:40 ` Takahiro Yasui
2009-06-27 0:18 ` Takahiro Yasui [this message]
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=4A45656E.4050903@redhat.com \
--to=tyasui@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--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;
as well as URLs for NNTP newsgroup(s).