All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tore Anderson <tore@linpro.no>
To: dm-devel@redhat.com
Subject: Using different configuration for arrays with identical vendor/product
Date: Fri, 28 Mar 2008 12:23:30 +0100	[thread overview]
Message-ID: <47ECD532.5060402@linpro.no> (raw)

Hey.  I've got an EMC CX200 and a CX3-40 in my SAN.  The latter one
supports ALUA, which I'm using as much as I can, the former does not.
The hosts need to be able to access volumes on both the arrays at the
same time.

Unfortunately the volumes on both of these boxes have vendor «DGC» and
product «RAID 5», so making two different device sections for them with
different hardware_handler and path_checker settings isn't trivial.  I
figured I could simply override the two settings in the multipath{}
blocks for volumes on the CX200, making the device{} block specific for
the CX3-40.  Doesn't appear to work, though, the path_checker- and
hardware_handler-settings in the multipath{} blocks appears to be
silently ignored.

Am I out of luck or is there any other way to do what I want?

For reference, this is the device section I use for the CX200 in
standard «trespassing» mode:

device {
  vendor               DGC.*
  product              RAID.*
  hardware_handler     "1 emc"
  path_checker         emc_clariion
  prio_callout         "/sbin/mpath_prio_emc /dev/%n"
  features             "1 queue_if_no_path"
  path_grouping_policy group_by_prio
  failback             immediate
}

And for the CX3-40 in ALUA mode:

device {
  vendor               DGC.*
  product              RAID.*
  hardware_handler     "0"
  path_checker         tur
  prio_callout         "/sbin/mpath_prio_emc /dev/%n"
  features             "1 queue_if_no_path"
  path_grouping_policy group_by_prio
  failback             immediate
}

These both work fine on hosts that only connect to one of the arrays at
a time.

Regards
-- 
Tore Anderson

             reply	other threads:[~2008-03-28 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 11:23 Tore Anderson [this message]
2008-03-28 16:25 ` Using different configuration for arrays with identicalvendor/product berthiaume_wayne
2008-03-28 23:07   ` 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=47ECD532.5060402@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.