From: Mike Anderson <andmike@us.ibm.com>
To: "chandrasekhar.nagaraj" <chandrasekhar.nagaraj@patni.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem created by Zoning on Linux
Date: Mon, 31 Mar 2003 09:46:01 -0800 [thread overview]
Message-ID: <20030331174601.GA1408@beaverton.ibm.com> (raw)
In-Reply-To: <000001c2f780$da0265e0$e9bba5cc@patni.com>
chandrasekhar.nagaraj [chandrasekhar.nagaraj@patni.com] wrote:
> But the second Host, which should have access to LUN 4 to 7, has some
> problem.
> The /proc/partitions does not show any scsi device file. Also
> /proc/scsi/scsi does not entries corresponding to LUN 4 to 7; but it have
> only one entry corresponding to LUN 0 (which should not be allowed).
>
> So, is there any restriction on Linux that the LUN number should start with
> 0 only??
> If so, then what is the solution/workaround?
You did not mention the kernel version you are working with, but I will
assume that it is 2.4 based (2.5 supports report_luns and should avoid
this problem).
The failure looks like you need to set a sparse lun flag for this
storage device. Add an entry with the BLIST_SPARSELUN flag set to the
device_list array in scsi_scan.c for this storage device.
If the scanning is happening post boot you could turn on some scan
logging to verify this issue.
echo "scsi log scan 4" > /proc/scsi/scsi
You can set logging during boot, but you can only control all logging or
none and it sometimes generates to much output.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2003-03-31 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 12:27 chandrasekhar.nagaraj
2003-03-31 14:40 ` James Bourne
2003-03-31 17:46 ` Mike Anderson [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=20030331174601.GA1408@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=chandrasekhar.nagaraj@patni.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®