From: Michael Clark <michael@metaparadigm.com>
To: jbradford@dial.pipex.com, GrandMasterLee <masterlee@digitalroadkill.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: QLogic Linux failover/Load Balancing ER0000000020860
Date: Sun, 06 Oct 2002 20:26:26 +0800 [thread overview]
Message-ID: <3DA02BF2.2040506@metaparadigm.com> (raw)
In-Reply-To: 200210061103.g96B3mlO001484@darkstar.example.net
>>I see. ATM I'm using 2.4.19, but would like to get to 2.4.20, because of
>>the TG3 fixes.
>
>
> You were probably thinking of CONFIG_SCSI_MULTI_LUN above, then. That causes the kernel to probe all LUNs instead of just LUN 0, which is the default due to a lot of broken devices to respond to all LUNs instead of just LUN 0. The sparse LUN option is in addition to that in 2.5.x.
>
> If this is for a live server, it might be easiest to hard code the LUNs you need it to probe in to 2.4.x for now, and wait until 2.6.x for proper support.
2.4 supports sparse lun scanning, although it is not enabled
dynamically and requires add a BLIST_SPARSELUN flag for your device
in the device_list array in drivers/scsi/scsi_scan.c
You just need to get the Vendor and Model info from /proc/scsi/scsi
I am using qlogic 2300s with sparse luns working fine on 2.4.18.
~mc
next prev parent reply other threads:[~2002-10-06 12:21 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
2002-10-06 10:31 ` GrandMasterLee
2002-10-06 11:03 ` jbradford
2002-10-06 12:26 ` Michael Clark [this message]
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=3DA02BF2.2040506@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=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