From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: RDAC path checker status change messages
Date: Wed, 3 Nov 2010 17:09:18 -0400 [thread overview]
Message-ID: <20101103210918.GB26473@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906231548060.18687@e-smith.charlieb.ott.istop.com>
This patch still seems relevant to upstream multipath-tools and is
available in dm-devel's patchwork here:
https://patchwork.kernel.org/patch/32081/
On Tue, Jun 23 2009 at 3:50pm -0400,
Charlie Brady <charlieb-dm-devel@budge.apana.org.au> wrote:
>
> It seems to me that this patch is required, to fix a problem with
> "path down" messages being logged when the path transitions to up
> (and presumably ghost).
>
> --- libcheckers/rdac.c.orig 2009-06-23 15:38:05.371422000 -0400
> +++ libcheckers/rdac.c 2009-06-23 15:39:28.020843000 -0400
> @@ -105,5 +105,12 @@
> return PATH_DOWN;
> }
>
> - return ((inq.avtcvp & 0x1) ? PATH_UP : PATH_GHOST);
> + if (inq.avtcvp & 0x1) {
> + MSG(c, MSG_RDAC_UP);
> + return PATH_UP;
> + }
> + else {
> + MSG(c, MSG_RDAC_GHOST);
> + return PATH_GHOST;
> + }
> }
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2010-11-03 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 19:50 RDAC path checker status change messages Charlie Brady
2009-06-24 18:15 ` Chandra Seetharaman
2009-06-24 20:19 ` Charlie Brady
2009-06-24 21:01 ` Benjamin Marzinski
2009-06-25 16:57 ` Charlie Brady
2009-06-25 17:02 ` Charlie Brady
2009-06-25 17:28 ` Charlie Brady
2009-06-26 16:07 ` Benjamin Marzinski
2009-06-25 18:29 ` Chandra Seetharaman
2009-06-25 18:40 ` Charlie Brady
2010-11-03 21:09 ` Mike Snitzer [this message]
2010-11-03 22:16 ` Christophe Varoqui
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=20101103210918.GB26473@redhat.com \
--to=snitzer@redhat.com \
--cc=christophe.varoqui@gmail.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.