All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Clariion CX600 automatic failback support
Date: Mon, 31 Oct 2005 17:06:52 +0100	[thread overview]
Message-ID: <20051031160652.GB31532@free.fr> (raw)
In-Reply-To: <1130773899.4071.18.camel@brilong-lnx>

On Mon, Oct 31, 2005 at 10:51:38AM -0500, Brian Long wrote:
> On Mon, 2005-10-31 at 15:07 +0100, Christophe Varoqui wrote:
> > > 
> > > No one has automatic failback working on Clarrion storage?
> > > 
> > Do you reproduce with upstream ?
> 
> No.  I imagine we will log a support request with Red Hat to get it
> working on RHEL 4 U2.  If they want to give us an updated device-mapper-
> multipath RPM to try to reproduce with upstream, that's up to them.
> Phil and I were just wondering if there is a specific configuration
> parameter to get the trespass to happen again once all paths are back
> online.
> 
Every check interval, the daemon re-evaluates path priorities (through
external prioritizers), then re-compute path-groups priorities. If PG
priority order change, the highest-prio PG might be activated :

- immediatly, if "failback" is set to immediate
- never, if "failback" is set to manual
- in a number of prio-order stable consecutive checks, if failback
  set to #

Thus, failback/no-failback is a property of the external prioritizer, plus
a framework policy switch in the name of the "failback" config file keyword.

Well, at least it is the current design upstream.
You'll have to dig the changelog to see if RedHat packages all the
necassary bits.

Regards,
cvaroqui

  reply	other threads:[~2005-10-31 16:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 19:37 Clariion CX600 automatic failback support Phil Lowden (plowden)
2005-10-31 13:58 ` Brian Long
2005-10-31 14:02   ` Bernd Zeimetz
2005-10-31 14:07   ` Christophe Varoqui
2005-10-31 15:51     ` Brian Long
2005-10-31 16:06       ` Christophe Varoqui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 21:32 goggin, edward
2005-11-03 13:58 ` Christophe Varoqui
2005-11-07 19:25 ` Benjamin Marzinski
2005-11-03 18:16 goggin, edward
2005-11-03 20:55 ` Brian Long
2005-11-03 22:00   ` Bernd Zeimetz
2005-11-04  8:19 ` Bernd Zeimetz
2005-11-04  9:47   ` Christophe Varoqui
2005-11-04 19:36 goggin, edward
2005-11-04 20:55 ` Christophe Varoqui
2005-11-05  0:03   ` Bernd Zeimetz
2005-11-05 12:26     ` Christophe Varoqui
2005-11-10 19:24       ` Bernd Zeimetz
2005-11-06 18:29 goggin, edward

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=20051031160652.GB31532@free.fr \
    --to=christophe.varoqui@free.fr \
    --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.