public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederik Schueler <fs@lowpingbastards.de>
To: Christoph Hellwig <hch@infradead.org>,
	Frederik Schueler <fs@lowpingbastards.de>,
	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 14:48:03 +0200	[thread overview]
Message-ID: <20050824124803.GE13391@mail.lowpingbastards.de> (raw)
In-Reply-To: <20050824100112.GA27216@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 795 bytes --]

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.

Thanks anyway :)
Frederik Schueler

-- 
ENOSIG

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-24 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 11:25 new qla2xxx driver breaks SAN setup with 2 controllers Frederik Schueler
2005-08-23 20:00 ` Patrick Mansfield
2005-08-24  9:55   ` Frederik Schueler
2005-08-24 10:01     ` Christoph Hellwig
2005-08-24 12:48       ` Frederik Schueler [this message]
2005-08-24 12:50         ` Christoph Hellwig
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=20050824124803.GE13391@mail.lowpingbastards.de \
    --to=fs@lowpingbastards.de \
    --cc=hch@infradead.org \
    --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