From: Michael Clark <michael@metaparadigm.com>
To: manjuanth n <manju_tt@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: need help
Date: Sun, 09 Jun 2002 03:43:12 +0800 [thread overview]
Message-ID: <3D025E50.1020506@metaparadigm.com> (raw)
In-Reply-To: <20020608112710.23692.qmail@web14403.mail.yahoo.com>
2.4.18 needs a hint added to drivers/scsi/scsi_scan.c
to allow it to scan targets with sparse luns.
Look in /proc/scsi/scsi for the vendor and model and
add them into the device_list array in scsi_scan.c
...
{"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
If you don't configure lun 0, you may have to use
BLIST_FORCELUN which if my understanding is correct
will force scanning of all luns.
I hear there is some REPORT_LUNS code that will
eliminate the need to do this, although don't know
which kernel has it.
~mc
On 06/08/02 19:27, manjuanth n wrote:
>Dear sir,
> we have SAN environment with hitachi storage box
>and brocade switch. we are trying to install Linux
>with qlogic HBA card. we are facing strange
>problems
>1. If we disable LUN 0 we will not be able to see
>any LUNs on liunx machine
>2. If we enable LUN 0 we can see all the LUNS
>but it should be in sequence i.e LUN0 ,1,2 , 3 etc
>if we disable LUN 3 we will not be able to see LUNS
>4 and the rest
> Is the above things are limitation of linux.
>Linux machine is running with 2.4.18 kernel
>
>Is there any solutions for these problems?
>
>Thanks and Regards
>Manjuanth
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! - Official partner of 2002 FIFA World Cup
>http://fifaworldcup.yahoo.com
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2002-06-08 19:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 11:27 need help manjuanth n
2002-06-08 19:43 ` Michael Clark [this message]
2002-06-10 14:21 ` manjuanth n
2002-06-10 17:04 ` Patrick Mansfield
2002-06-13 14:25 ` manjuanth n
2002-06-13 14:25 ` manjuanth n
[not found] <3D04BA0E.7000702@metaparadigm.com>
2002-06-13 14:21 ` manjuanth n
2002-06-13 14:21 ` manjuanth n
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 7:51 Pius Jerry
2003-10-30 9:30 ` Nick Piggin
2007-04-06 7:49 vjn
2007-04-08 18:00 ` Bill Davidsen
[not found] <86Xi2-6La-421@gated-at.bofh.it>
2007-04-06 21:24 ` Bodo Eggert
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=3D025E50.1020506@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manju_tt@yahoo.com \
/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