From: "Josef Möllers" <josef.moellers@fujitsu-siemens.com>
To: "Zuylen, G. van" <GvZuylen@ysl.nl>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: Problems with higher SCSI LUN's with SLES8
Date: Wed, 17 Sep 2003 09:15:28 +0200 [thread overview]
Message-ID: <3F680A10.D2658EF4@fujitsu-siemens.com> (raw)
In-Reply-To: A00BBCF927F25E4A9D5F6EE1380CDEF2CC88@hedwig.ysl.nl
"Zuylen, G. van" wrote:
>
> Hi you all,
>
> We are using a HP DL380 server with a Qlogic 2300 HBA adapter. This adapter
> is connected to a HP EMA12000 SAN (with HSG80 controllers). Behind the HBA
> (qlogic 2300) we see only the devices up to LUN 7, higher LUN are not
> detected. We have tried several things like modifying /etc/modules.conf with
> "options scsi_mod max_scsi_luns=128" and modifying /boot/grub/menu.lst. But
> nothing seems to be working.
> We are using SLES8 with kernel version k_smp-2.4.19-304 and the qlogic
> driver version 6.05.60. Also tested with a newer kernel k_smp-2.4.19-340,
> but this makes no difference.
>
> Does anybody know how we can solve this problem or is there somebody who has
> experience with this ?
What does /proc/scsi/scsi say about the ANSI SCSI revision? If it says
"02", then you'll need to change the scsi mid-layer: the current code
(and even future code B-{( will not scan beyond ID 7 on SCSI-2 devices.
--
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2003-09-17 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 7:48 Problems with higher SCSI LUN's with SLES8 Zuylen, G. van
2003-09-04 8:14 ` Christoph Hellwig
2003-09-04 23:43 ` Andrew Patterson
2003-09-17 1:05 ` phil
2003-09-17 7:15 ` Josef Möllers [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=3F680A10.D2658EF4@fujitsu-siemens.com \
--to=josef.moellers@fujitsu-siemens.com \
--cc=GvZuylen@ysl.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.