From: Kurt Garloff <garloff@suse.de>
To: Austin Gonyou <austin@digitalroadkill.net>
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: Wed, 26 Jun 2002 18:07:45 +0200 [thread overview]
Message-ID: <afcp0u$f4k$2@main.gmane.org> (raw)
In-Reply-To: <1025101125.19558.4.camel@UberGeek>
[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]
Hi Austin,
On Wed, Jun 26, 2002 at 09:18:45AM -0500, Austin Gonyou wrote:
> On Wed, 2002-06-26 at 07:33, Kurt Garloff wrote:
> > enough guesses have been there not answering your questions ...
>
> Sure I hear that. But I posted an earlier question about QLA2200 and a
You don't think that somebody who reads your message and tries to post a
helpful comment scans the list for earlier messages of yours, do you?
> PV 660F and not seeing > 8 luns with 2.4.19-pre10.
^^^^^^^
This device needs BLIST_LARGELUN.
> I'll take a look at that, and see if I can merge it into -aa4.
The patch should be in there, just not the additional devices that need
BLIST_LARGELUN.
> > 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.
>
> This would be a DELL device, so I'll see about changing it from
> SPARESLUN to LARGELUN?
No. Add " | BLIST_LARGELUN" .
> > 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 ...
>
> There's nothing to post from /proc/scsi/scsi or the syslog other than
> there's no more than 8 devices on my FC chain. I guess the real point
> here is that if you're using FC, you're probably going to use more than
> 8 luns, even if not immediately. Especially for large Databases.
People could have seen what SCSI device you're using.
So I could have told you instead of guessing and risking to add to the noise
myself.
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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-06-26 16:07 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 [this message]
[not found] ` <20020626160745.GF3023@gum01m.etpnet.phys.tue.nl>
2002-06-26 17:50 ` Austin Gonyou
2002-06-26 14:32 ` Austin Gonyou
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='afcp0u$f4k$2@main.gmane.org' \
--to=garloff@suse.de \
--cc=austin@digitalroadkill.net \
--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