From: "Eric Moore" <emoore@lsil.com>
To: linux-scsi@vger.kernel.org, Maurice Volaski <mvolaski@aecom.yu.edu>
Subject: Re: Why is the kernel complaining about large SCSI LUNs
Date: Fri, 7 Jan 2005 09:16:14 -0700 [thread overview]
Message-ID: <008001c4f4d4$364d0d80$111015ac@ericmoore> (raw)
In-Reply-To: a06100533be0463eff562@[129.98.90.227]
The mpt fusion driver supports 256 luns,
and it seems your device supports more than that.
Eric
On Friday, January 07, 2005 9:07 AM, Maurice Volaski wrote:
> I am running kernel 2.6.9 on an Opteron box with an LSI 320 card and
> am seeing the following message repeatedly in dmesg:
>
> scsi: host 1 channel 0 id 0 lun 0x5a5a5a5a5a5a5a5a has a LUN larger
> than currently supported.
>
> Is this just cosmetic or there is a bug somewhere? It appears that
> scsi_scan.c has logic where this message is actually valid, but how
> can that be?
> --
>
> Maurice Volaski, mvolaski@aecom.yu.edu
> Computing Support, Rose F. Kennedy Center
> Albert Einstein College of Medicine of Yeshiva University
> -
> 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
>
next prev parent reply other threads:[~2005-01-07 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 16:07 Why is the kernel complaining about large SCSI LUNs Maurice Volaski
2005-01-07 16:16 ` Eric Moore [this message]
2005-01-07 16:22 ` Arjan van de Ven
2005-01-07 16:30 ` James Bottomley
2005-01-07 23:25 ` Maurice Volaski
2005-01-07 23:37 ` James Bottomley
2005-01-08 0:07 ` Maurice Volaski
2005-01-08 1:27 ` Douglas Gilbert
2005-01-08 1:57 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2005-01-08 0:59 Moore, Eric Dean
2005-01-12 23:12 Maurice Volaski
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='008001c4f4d4$364d0d80$111015ac@ericmoore' \
--to=emoore@lsil.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mvolaski@aecom.yu.edu \
/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