From: Christoph Hellwig <hch@infradead.org>
To: Frederik Schueler <fs@lowpingbastards.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Patrick Mansfield <patmans@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: new qla2xxx driver breaks SAN setup with 2 controllers
Date: Wed, 24 Aug 2005 13:50:22 +0100 [thread overview]
Message-ID: <20050824125022.GA29817@infradead.org> (raw)
In-Reply-To: <20050824124803.GE13391@mail.lowpingbastards.de>
On Wed, Aug 24, 2005 at 02:48:03PM +0200, Frederik Schueler wrote:
> Hello,
>
> On Wed, Aug 24, 2005 at 11:01:12AM +0100, Christoph Hellwig wrote:
> > > yes exactly, only the bootdrive LUN is registered after bootup. I have
> > > to selectively scsiadd the other LUNs if there is a gap between the
> > > boot LUN (1-8 in our setup) and the shared storages (9-14). I don't
> > > consider this a bug though, I had to remove some devices otherwise,
> > > and old drivers had to be patched to allow this at all.
> >
> > Actually this sounds like a bug in your storage system. It's probably
> > reporting to be only SCSI2 complicant, which doesn't make sense for
> > FC storage. Please try the patch below:
>
> [...]
>
> Unfortunately this does not fix this issue, besides the SAN being
> reported as a scsi3 device now.
Cane you add BLIST_SPARSELUN and BLIST_LARGELUN to the flags aswell?
next prev parent reply other threads:[~2005-08-24 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050823112535.GB13391@mail.lowpingbastards.de>
2005-08-23 20:00 ` new qla2xxx driver breaks SAN setup with 2 controllers Patrick Mansfield
2005-08-24 9:55 ` Frederik Schueler
2005-08-24 10:01 ` Christoph Hellwig
2005-08-24 12:48 ` Frederik Schueler
2005-08-24 12:50 ` Christoph Hellwig [this message]
2005-08-24 13:08 ` Frederik Schueler
2005-08-24 17:03 ` Patrick Mansfield
2005-08-25 11:42 ` Frederik Schueler
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=20050824125022.GA29817@infradead.org \
--to=hch@infradead.org \
--cc=fs@lowpingbastards.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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;
as well as URLs for NNTP newsgroup(s).