From: Tore Anderson <tore@linpro.no>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Round Robin vs Active/Passive
Date: Thu, 22 May 2008 13:57:10 +0200 [thread overview]
Message-ID: <48355F96.8040603@linpro.no> (raw)
In-Reply-To: <000301c8bbe5$4f1091d0$cf42e3c1@pitagora.it>
* Domenico Viggiani
> Sorry for question: is this how new ALUA mode works for EMC Clariion
> CX arrays?
Yes, that's right. Except for the fact that mpath_prio_emc will
correctly detect the preferred controller, while mpath_prio_hds_modular
only checks even/odd LUNs.
> Are default settings suitable for this new failover mode?
You don't have to use the EMC specific hardware handler or path checker
any longer. This is what I use for my CX3:
device {
vendor DGC
product *
product_blacklist LUNZ
path_grouping_policy group_by_prio
path_checker tur
no_path_retry queue
prio_callout "/sbin/mpath_prio_emc /dev/%n"
failback immediate
}
Note that the host is no longer able to explicitly trespass the volume
between controllers. I actually see that as an advantage, especially in
cluster environments. If the host wants to change controllers it can
simply do so and wait for the CX to implicitly trespass the volume (due
to the I/O coming mostly to the passive controller). This works very
well, and I consider it a huge improvement over the old
Passive-Not-Ready mode you had to use earlier (hwhandler "emc").
Note that there's also a new ALUA-specific hardware handler available
now. I never tried it, so I can't tell how it differs from my setup.
Regards,
--
Tore Anderson
next prev parent reply other threads:[~2008-05-22 11:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a6b34b03e0524aa66c862534fee9b7a@www3.mail.volny.cz>
2008-05-21 11:41 ` INFO: task md2_resync:7950 blocked for more than 120 seconds Neil Brown
2008-05-21 14:48 ` Round Robin vs Active/Passive Craig Simpson
2008-05-21 15:32 ` Craig Simpson
2008-05-21 18:23 ` Tore Anderson
2008-05-21 20:21 ` Craig Simpson
2008-05-21 21:01 ` Tore Anderson
2008-05-21 21:49 ` Craig Simpson
2008-05-21 23:41 ` Craig Simpson
2008-05-22 12:00 ` Tore Anderson
2008-05-22 8:24 ` Domenico Viggiani
2008-05-22 11:57 ` Tore Anderson [this message]
2008-05-23 7:16 ` Hannes Reinecke
2008-05-23 8:00 ` Tore Anderson
2008-05-23 8:55 ` Hannes Reinecke
2008-05-23 9:42 ` Tore Anderson
2008-05-23 10:36 ` Domenico Viggiani
2008-05-23 10:46 ` Tore Anderson
2008-05-23 21:16 ` Sebastian Herbszt
2008-06-05 6:54 ` Tore Anderson
2008-06-05 7:20 ` Hannes Reinecke
2008-06-06 7:19 ` Tore Anderson
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=48355F96.8040603@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.