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: defining paths with DDN 8500
Date: Thu, 13 Sep 2007 10:33:11 +0200	[thread overview]
Message-ID: <46E8F5C7.6050005@linpro.no> (raw)
In-Reply-To: <43123.80742.qm@web51104.mail.re2.yahoo.com>

* Mike White

> I'm working with the multipathing package and a DDN 8500.  I've been
> able to successfully configure  failover and failback.  The system is
> configured as such:
>     qla_port_1 ----  ctrl A port 4 ---- LUN 3 (LUN 7)
>     qla_port_2 ----  ctrl B port 4 ---- LUN 7 (LUN 3)
> 
> Where LUN 3 is on a dedicated port to qla_port_1 and qla_port_2 is
> dedicated to LUN 7.
> 
> The problem that I'm having is all the traffic is going through
> qla_port_1, qla_port_2 appears to be sitting idle until a failover.
> 
> To compensate, I've been using dmsetup to force the qla_port_2 ----
> LUN 7 path.
> 
> Is there a better way than using dmsetup to do this?  multipath isn't
> an option, as it negatively impacts performance.

  Sounds like you're in need of a prio_callout.  I'm not familiar with
 your hardware so I don't know if there's already one available, if not,
 make a simple script that for example prints "2" for the paths you want
 to prefer and "1" for the ones you want to use as backups.  Then set
 path_grouping_policy to "failover".  You might also want to set
 failback to "immediate".

Regards
-- 
Tore Anderson

  reply	other threads:[~2007-09-13  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 22:38 defining paths with DDN 8500 Mike White
2007-09-13  8:33 ` Tore Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13 21:59 Mike White

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=46E8F5C7.6050005@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.