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 12:50:19 -0500 [thread overview]
Message-ID: <1025113819.22762.5.camel@UberGeek> (raw)
In-Reply-To: <20020626160745.GF3023@gum01m.etpnet.phys.tue.nl>
On Wed, 2002-06-26 at 11:07, Kurt Garloff wrote:
> 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?
>
Well, I do, especially if someone says it's an urgent thing to try and
get the whole story. If I don't have time, I'll ask someone to give more
info, which you did and I respect that and thank you.
> > PV 660F and not seeing > 8 luns with 2.4.19-pre10.
> ^^^^^^^
>
> This device needs BLIST_LARGELUN.
I got that from your earlier post and addressed it directly. Thanks for
the pointer. I didn't know the 660 was defined explicitly in the
scsi_scan.c I've since recompiled several kernel versions to assert this
as being true with the BLIST_LARGELUN option and it's definitely fixed
my problems there.
> > 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" .
Yep, Did that. Again Thanks!
> > > 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.
I hear you loud and clear. I wouldn't have made so much noise myself had
it not been a *top* priority item that I couldn't find info on anywhere
else, plus the boss putting pressure too. Soon, this system will be a
6650 with PV 660F, 8GB RAM, using Linux with Oracle8.1.7.2, XFS, 0(1)
scheduler and nearly a TB of total DB.
I have some results from my benchmarking which are quite astounding too.
> 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>
next prev parent reply other threads:[~2002-06-26 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 0:46 max_scsi_luns and 2.4.19-pre10 Austin Gonyou
2002-06-26 1:50 ` Urgent, Please respond - " Austin Gonyou
2002-06-26 2:48 ` jw schultz
2002-06-26 3:05 ` Austin Gonyou
2002-06-26 3:47 ` jw schultz
2002-06-26 4:03 ` Austin Gonyou
2002-06-26 4:50 ` >8 luns on 2.4.19-pre10-aa4 Austin Gonyou
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
2002-06-26 17:50 ` Austin Gonyou [this message]
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=1025113819.22762.5.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