From: Patrick Mansfield <patmans@us.ibm.com>
To: Kurt Garloff <garloff@suse.de>,
Patrick Mansfield <patmans@us.ibm.com>,
Fabien Salvi <fabien@cri74.org>,
linux-scsi@vger.kernel.org,
Lorraine Suschetet <lorraine@ext.cri74.org>
Subject: Re: Pb with external RAID controller in lk 2.4
Date: Fri, 24 May 2002 10:44:50 -0700 [thread overview]
Message-ID: <20020524104450.B22142@eng2.beaverton.ibm.com> (raw)
In-Reply-To: <20020524191733.N28936@gum01m.etpnet.phys.tue.nl>; from garloff@suse.de on Fri, May 24, 2002 at 07:17:33PM +0200
On Fri, May 24, 2002 at 07:17:33PM +0200, Kurt Garloff wrote:
> Hi Patrick,
>
> On Wed, May 22, 2002 at 10:03:39AM -0700, Patrick Mansfield wrote:
> > The 2.4 kernel won't scan past LUN 7 for SCSI-2 devices - you can try
> > modifying the code and set the max to 31 in scsi_scan.c.
>
> If you have a FC device (or whatever device that supports LUNs > 7) that
> reports as SCSI-2, you can flag it with BLIST_LARGELUN in scsi_scan.c
> to get it treated as SCSI-3.
> (New in 2.4.18)
I don't see that in 2.4.18, is it in a 2.4.19-pre? (I can't get to
any kernel.org or a mirror right now.)
> > /* Use the peripheral qualifier field to determine online/offline */
> > if (((scsi_result[0] >> 5) & 7) == 1) SDpnt->online = FALSE;
> > else SDpnt->online = TRUE;
> Those fields should not be set by the device, IMHO.
> Or has their meaning changed for SCSI-3 devs? Then the appropriate check
> should be added to the code.
I don't think anything has changed, SCSI-3 for a peripheral qualifier
of 001b says:
The device server is capable of supporting the specified peripheral device
type on this logical unit. However, the physical device is not currently
connected to this logical unit.
So it seems reasonable to set it to 1. For many disk arrays, this value
can be modified - the pq or byte one of the INQUIRY result for LUNs with
with no storage.
-- Patrick Mansfield
>
> > The device is probably setting the peripheral-qualifier (PQ) such that the
> > scan continues but the device is marked offline, this is just annoying
> > if do not have a lot of them. In scsi_scan.c:
> >
>
> But actually the problem is different: Too many LUNs where detected :-(
>
> Regards,
> --
> Kurt Garloff <garloff@suse.de> Eindhoven, NL
> GPG key: See mail header, key servers Linux kernel development
> SuSE Linux AG, Nuernberg, DE SCSI, Security
next prev parent reply other threads:[~2002-05-24 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 17:28 Pb with external RAID controller in lk 2.4 Fabien Salvi
2002-05-22 0:03 ` Gérard Roudier
2002-05-22 1:03 ` Douglas Gilbert
2002-05-22 7:49 ` Fabien Salvi
2002-05-22 17:03 ` Patrick Mansfield
2002-05-23 9:01 ` Fabien Salvi
2002-05-24 17:17 ` Kurt Garloff
2002-05-24 17:44 ` Patrick Mansfield [this message]
2002-05-24 17:55 ` Kurt Garloff
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=20020524104450.B22142@eng2.beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=fabien@cri74.org \
--cc=garloff@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=lorraine@ext.cri74.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