All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Brier <jbrier@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Question regarding failback option in multipath.conf
Date: Wed, 30 Sep 2009 15:24:52 -0400	[thread overview]
Message-ID: <4AC3B084.4060700@redhat.com> (raw)
In-Reply-To: <06F122DE-B7E5-4721-BA08-D0453D10581C@aclue.com>

On 09/30/2009 03:16 PM, Eli Klein wrote:
>
> Here's the abbreviated output from multipath -v3:
>
> mpath1: pgfailback = 120 (config file default)
> mpath1: pgpolicy = multibus (config file default)
> mpath1: selector = round-robin 0 (internal default)
> mpath1: features = 1 queue_if_no_path (internal default)
> mpath1: hwhandler = 0 (internal default)
> mpath1: rr_weight = 2 (config file default)
> mpath1: minio = 10 (config file default)
> mpath1: no_path_retry = 1 (config file default)
> pg_timeout = NONE (internal default)
> mpath1: set ACT_NOTHING (map unchanged)
>
> It's definitely picking up the settings correctly from multipath.conf,
> but the paths are still reinstated immediately once they're reconnected
> (even if it's just for a split second).
>

What does /var/log/messages look like when this happens? Since you 
changed failback to 120 did you restart multipathd or restart the box?

John Brier

  reply	other threads:[~2009-09-30 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 16:41 Question regarding failback option in multipath.conf Eli Klein
2009-09-30 18:51 ` Eli Klein
2009-09-30 19:07 ` John Brier
2009-09-30 19:16   ` Eli Klein
2009-09-30 19:24     ` John Brier [this message]
2009-09-30 19:36       ` Eli Klein
2009-10-01 21:16         ` Eli Klein
2009-10-02  0:39           ` John A. Sullivan III
2009-10-02  1:01             ` Eli Klein
2009-10-02 14:30               ` John Brier
2009-10-02 14:40                 ` Eli Klein

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=4AC3B084.4060700@redhat.com \
    --to=jbrier@redhat.com \
    --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.