From: Frederik Schueler <fs@lowpingbastards.de>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Frederik Schueler <fs@lowpingbastards.de>,
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 11:55:20 +0200 [thread overview]
Message-ID: <20050824095520.GD13391@mail.lowpingbastards.de> (raw)
In-Reply-To: <20050823200040.GA8310@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hello,
On Tue, Aug 23, 2005 at 01:00:40PM -0700, Patrick Mansfield wrote:
> The use of scsiadd script implies that you are attaching or somehow
> modifying the storage after the driver has loaded. Is that correct?
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.
> There is a fix for scanning initiated via user space, this change:
>
> http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=5c44cd2afad3f7b015542187e147a820600172f1
>
> The above fix is in the current 2.6 git tree. Does that fix your problem?
It does, thanks for the hint :-)
I see this is in rc7 too.
> Also try using lsscsi.
it does not list the non-registered LUNs the driver knows about, as the
old proc interface did.
Best regards
Frederik Schueler
--
ENOSIG
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-24 9:55 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 [this message]
2005-08-24 10:01 ` Christoph Hellwig
2005-08-24 12:48 ` Frederik Schueler
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=20050824095520.GD13391@mail.lowpingbastards.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.