From: Christoph Hellwig <hch@infradead.org>
To: "jansen, frank" <jansen_frank@emc.com>
Cc: "'Josef Möllers'" <josef.moellers@fujitsu-siemens.com>,
"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, 8 Aug 2003 13:15:43 +0100 [thread overview]
Message-ID: <20030808131543.A5698@infradead.org> (raw)
In-Reply-To: <64655AAA92E6ED46B9AC9421260D96A5025BD653@srmanning.lss.emc.com>; from jansen_frank@emc.com on Fri, Aug 08, 2003 at 08:13:11AM -0400
On Fri, Aug 08, 2003 at 08:13:11AM -0400, jansen, frank wrote:
> The delineation between the EMC boxes that require vs. not require
> a "TRESPASS" command lies not with their age, but rather their family.
> The CLARiiON family of Storage Arrays require a "TRESPASS" command to
> move a LUN from one redundant Storage Processor (SP) to another. On the
> other hand, Symmetrix Storage Arrays do not use any such behavior. In
> a nutshell, the Symmetrix is active on all paths, on which the LUN is
> presented, whereas the CLARiiON is active on one SP and passive on the
> other SP.
So it's rather DG arrays vs EMC ones, ok.
next prev parent reply other threads:[~2003-08-08 12:15 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 [this message]
2003-08-08 12:21 ` Josef Möllers
-- 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=20030808131543.A5698@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--cc=jansen_frank@emc.com \
--cc=josef.moellers@fujitsu-siemens.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