From: Austin Gonyou <austin@digitalroadkill.net>
To: Kurt Garloff <garloff@suse.de>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: max_scsi_luns and 2.4.19-pre10.
Date: 26 Jun 2002 09:32:27 -0500 [thread overview]
Message-ID: <1025101947.19700.15.camel@UberGeek> (raw)
In-Reply-To: <20020626123337.GC1217@gum01m.etpnet.phys.tue.nl>
On Wed, 2002-06-26 at 07:33, Kurt Garloff wrote:
> Hi Austin,
>
> enough guesses have been there not answering your questions ...
>
> On Tue, Jun 25, 2002 at 07:46:25PM -0500, Austin Gonyou wrote:
> > This originally was asking for help regarding QLA2200's, but I've since
> > discovered it's a kernel param problem that I'm not sure how to solve.
> >
> > Using a default RH kernel (from SGI XFS installer) and passing
> > max_scsi_luns=128 in grub, and for scsi_mod, it seems to work.
>
> In 2.4.19pre1 a patch was merged into mainline which introduced a flag
> BLIST_LARGELUN and set it for EMC Symmetrix devices. Some distributors
> (incl. RH and SuSE) did ship kernels with this patch included.
> http://van-dijk.net/linuxkernel/200206/0347.html
> (An older patch for 2.4.16 exists as well.)
Ahh...I see now. I looked for DELL in the scsi_scan.c and saw the
symmetrix there right above it. I should be able to add LARGELUN, since
it's #defined above and go for it. I'll see what this does, it's
starting to make sense now. TIA.
> The flag does allow a device to use more than 8 LUNs despite it reporting
> as SCSI Version 2 devices (which can not support more than 8 LUNs normally
> ...)
> The flag also needs to be set for some more devices, look for DGC, DELL, CMD
> and CNSi/CNSI devices that already have the BLIST_SPARSELUN flag.
>
> But as you did not post the output of /proc/scsi/scsi nor the syslog
> meesages from your SCSI subsystem nobody knows what devices you're using or
> what actually happens. Just speculations ...
>
> PS: The better list for such questions is linux-scsi@vger.kernel.org
>
> 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
--
Austin Gonyou <austin@digitalroadkill.net>
prev parent reply other threads:[~2002-06-26 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1025052385.19462.5.camel@UberGeek>
2002-06-26 12:33 ` max_scsi_luns and 2.4.19-pre10 Kurt Garloff
2002-06-26 14:18 ` Austin Gonyou
2002-06-26 16:07 ` Kurt Garloff
[not found] ` <20020626160745.GF3023@gum01m.etpnet.phys.tue.nl>
2002-06-26 17:50 ` Austin Gonyou
2002-06-26 14:32 ` Austin Gonyou [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=1025101947.19700.15.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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