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: Round Robin vs Active/Passive
Date: Fri, 23 May 2008 12:46:13 +0200	[thread overview]
Message-ID: <4836A075.9090008@linpro.no> (raw)
In-Reply-To: <000401c8bcc0$d29e94d0$cf42e3c1@pitagora.it>

* Domenico Viggiani

> Red Hat 4.6 defaults for EMC are:
>        device {
>                vendor                  "DGC"
>                product                 "*"
>                bl_product              "LUNZ"
>                path_grouping_policy    group_by_prio
>                getuid_callout          "/sbin/scsi_id -g -u -s"
>                prio_callout            "/sbin/mpath_prio_emc /dev/%n"
>                hardware_handler        "1 emc"
>                features                "1 queue_if_no_path"
>                path_checker            emc_clariion
>                failback                immediate
>        }
> (from  /usr/share/doc/device-mapper-multipath-0.4.5/multipath.conf.defaults)
> Why do you use different settings? Are they not "optimal"?

These settings are suitable for PNR mode (failover mode 1, where the
passive paths are unable to process I/O - this will show as large
amounts of I/O errors during boot).  When all paths to the currently
active  fail, dm-multipath will instruct the CX to move the volume from
the active controller to the passive one.  This is bad in cluster
environment, where two cluster nodes might have a differing opinion of
which controller should own the volume and you'll end up having a volume
that constantly moves back and forth between controllers.

My settings are better suited for ALUA mode (failover mode 4, all paths
are able to process I/O), especially if the ALUA-specific support in
dm-multipath isn't available due to old kernels or similar.  I sent an
email to the list one hour ago detailing the advantages I see with this
setup.

Unfortunately I have found no way to detect if an array is operating in
ALUA or PNR mode and have dm-multipath automatically apply different
device{} sections based on that.  I have some nodes that are connected
to both my CX3 and an old CX200 (which doesn't support ALUA), and due to
this I need to use PNR mode on the CX3 too, wich kinda sucks.  Time to
get rid of the CX200 I guess.

Regards,
-- 
Tore Anderson

  reply	other threads:[~2008-05-23 10:46 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
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 [this message]
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=4836A075.9090008@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.