From: "Josef Möllers" <josef.moellers@fujitsu-siemens.com>
To: "jansen, frank" <jansen_frank@emc.com>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Summary of the Multi-Path BOF at OLS and future directions
Date: Fri, 08 Aug 2003 14:21:03 +0200 [thread overview]
Message-ID: <3F3395AF.30C5CE21@fujitsu-siemens.com> (raw)
In-Reply-To: 64655AAA92E6ED46B9AC9421260D96A5025BD653@srmanning.lss.emc.com
"jansen, frank" wrote:
> > Without the TRESPASS, you'd see the LUN (INQUIRY), but you can't do
> > anything with it, even a simple READ CAPACITY fails.
>
> This is correct. Note, that it is not necessarily desirable to TRESPASS
> the LUN, as there may be an active path from the other SP to this or
> another HBA on the host system.
With MultiPath it _is_ necessary to TRESPASS a CLARiiON box if each SP
is conected to a seperate path.
--
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
-
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:[~2003-08-08 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 12:13 Summary of the Multi-Path BOF at OLS and future directions jansen, frank
2003-08-08 12:15 ` Christoph Hellwig
2003-08-08 12:21 ` Josef Möllers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 12:28 jansen, frank
2003-08-08 13:27 ` Josef Möllers
2003-08-05 3:54 James Bottomley
2003-08-05 16:48 ` Alan Cox
2003-08-05 17:06 ` James Bottomley
2003-08-07 11:00 ` Alan Cox
2003-08-06 0:14 ` Patrick Mansfield
2003-08-06 20:26 ` Steven Dake
2003-08-07 7:38 ` Lars Marowsky-Bree
2003-08-07 16:20 ` Christoph Hellwig
2003-08-07 23:54 ` Tim Pepper
2003-08-08 6:45 ` Josef Möllers
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=3F3395AF.30C5CE21@fujitsu-siemens.com \
--to=josef.moellers@fujitsu-siemens.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=jansen_frank@emc.com \
--cc=linux-scsi@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