All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tore Anderson <tore@linpro.no>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: CLARiiON failover modes and DM.
Date: Mon, 19 Nov 2007 19:51:28 +0100	[thread overview]
Message-ID: <4741DB30.8020009@linpro.no> (raw)
In-Reply-To: <940B4FF1F5958E4F96FC83C055A2F2611B8C5F@exch-2003.incipient.waltham>

* Paul Cote

> Is there a specific failover mode that the CX must be set for DM
> interoperability?

You have (at least) two options.  CLARiiON Open mode 1 is the 
traditional way where all paths to the passive controller is present but 
will refuse almost all I/O operations.  You'll need to be using the 
"emc" hardware handler for that to work, since a proprietary command 
needs to be sent to a path to the passive controller in order to 
trespass the volume there.

The other option (which is only available in FLARE 26) is ALUA mode 
(CLARiiON Open mode 4), where I/O is accepted on both controllers even 
though only one is the one handling all the I/O.  You can use this 
without a hardware handler (there's one in developement, though), but 
you'll still want to be prioritising the paths to the preferred 
controller for optimal performance.  This is the mode I would prefer, at 
least.  I wrote a bit more about the ALUA mode a few days ago:

http://thread.gmane.org/gmane.linux.kernel.device-mapper.devel/4366/focus=4435

Regards
-- 
Tore Anderson

  reply	other threads:[~2007-11-19 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 16:14 CLARiiON failover modes and DM Paul Cote
2007-11-19 18:51 ` Tore Anderson [this message]
2007-11-19 20:20   ` Paul Cote
2007-11-20  7:46     ` Tore Anderson
2007-11-20 18:59       ` Paul Cote
2007-11-21  7:20         ` Tore Anderson
2007-11-20 11:20 ` Stephan Austermühle

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=4741DB30.8020009@linpro.no \
    --to=tore@linpro.no \
    --cc=dm-devel@redhat.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.