From: Michael Clark <michael@metaparadigm.com>
To: Jim Zajkowski <jamesez@umich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sparse LUN scanning - 2.4.x
Date: Wed, 12 Jan 2005 17:50:19 +0800 [thread overview]
Message-ID: <41E4F2DB.4010806@metaparadigm.com> (raw)
In-Reply-To: <cs210t$l8m$1@sea.gmane.org>
Jim Zajkowski wrote:
> On 2005-01-11 19:07:53 -0500, Michael Clark <michael@metaparadigm.com>
> said:
>
>>> The problem is this: since LUN 0 does not show up -- specifically,
>>> it can't read the vendor or model informaton -- the kernel SCSI scan
>>> does not match with the table to tell the kernel to do sparse LUN
>>> scanning... so the RAID does not appear.
>>
>
>> Add the Xserve with the BLIST_SPARSELUN flag into the
>> blacklist/quirks table in drivers/scsi/scsi_scan.c
>
>
> It already is in the quirks list.
>
> The problem is that LUN 0 does not show up on this machine, so the
> quirks table doesn't work. Looking at /proc/scsi/scsi shows the
> device but only sorta:
>
Okay. I believe there is a patch floating around for 2.4 that is used in
some of the other distro's kernels that adds REPORT LUNS scanning as
well as a flag to force LUN scanning (although not sure it works if LUN
0 is not present).
A pragmatic solution may be to just add the echo scsi add-single-device
x x x x > /proc/scsi/scsi into your early boot or configure one of your
slices on LUN 0 (if the Xserve RAID allows that). 2.6 (and RHEL 4)
support the REPORT LUNS so should work there although there are some
messages on linux-scsi about the Xserve RAID's specific handling of LUN
0. Probably good idea to post to linux-scsi.
~mc
prev parent reply other threads:[~2005-01-12 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 19:05 Sparse LUN scanning - 2.4.x Jim Zajkowski
2005-01-12 0:07 ` Michael Clark
2005-01-12 2:11 ` Jim Zajkowski
2005-01-12 9:50 ` Michael Clark [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=41E4F2DB.4010806@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=jamesez@umich.edu \
--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