From: jbradford@dial.pipex.com
To: masterlee@digitalroadkill.net (GrandMasterLee)
Cc: linux-kernel@vger.kernel.org
Subject: Re: QLogic Linux failover/Load Balancing ER0000000020860
Date: Sun, 6 Oct 2002 11:19:09 +0100 (BST) [thread overview]
Message-ID: <200210061019.g96AJ9KA001206@darkstar.example.net> (raw)
In-Reply-To: <1033874298.4209.5.camel@localhost> from "GrandMasterLee" at Oct 05, 2002 10:18:45 PM
> > Linux is not allowed to address LUNs out of sequence, so searching for
> > further LUN numbers stops after 0, since 2 is the next one.
That's not true:
CONFIG_SCSI_REPORT_LUNS:
If you want to build with SCSI REPORT LUNS support i the kernel, say Y here.
The REPORT LUNS command is useful for devices (such as disk arrays) with large numbers of LUNs where the LUN values are not contiguous (sparse LUN).
REPORT LUNS scanning is done only for SCSI-3 devices.
> > Is there a way to resolve this, either at the driver level, IMHO the
> > place it *should* happen. At the storage level, the place that it could
> > also happen, or in the Kernel?
This is new in 2.5.x
John.
next prev parent reply other threads:[~2002-10-06 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41EBA11203419D4CA8EB4C6140D8B4017CD8EE@AVEXCH01.qlogic.org>
2002-10-06 0:09 ` QLogic Linux failover/Load Balancing ER0000000020860 Austin Gonyou
2002-10-06 3:18 ` GrandMasterLee
2002-10-06 10:19 ` jbradford [this message]
2002-10-06 10:31 ` GrandMasterLee
2002-10-06 11:03 ` jbradford
2002-10-06 12:26 ` Michael Clark
2002-10-06 19:40 ` GrandMasterLee
2002-10-06 23:14 ` GrandMasterLee
2002-10-07 4:54 ` GrandMasterLee
2002-10-07 5:15 ` Michael Clark
2002-10-07 5:24 ` GrandMasterLee
2002-10-06 7:58 ` Lars Marowsky-Bree
2002-10-07 16:32 ` Austin Gonyou
2002-10-06 15:45 James Bottomley
2002-10-06 19:46 ` GrandMasterLee
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=200210061019.g96AJ9KA001206@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.net \
/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