From: Benjamin Marzinski <bmarzins@redhat.com>
To: device-mapper development <dm-devel@redhat.com>,
Christophe Varoqui <christophe.varoqui@free.fr>
Subject: Re: multipath-tools libcheckers/tur.c libmultipath ...
Date: Tue, 21 Apr 2009 12:43:22 -0500 [thread overview]
Message-ID: <20090421174322.GV15911@ether.msp.redhat.com> (raw)
In-Reply-To: <20090421000525.23250.qmail@sourceware.org>
On Tue, Apr 21, 2009 at 12:05:25AM -0000, bmarzins@sourceware.org wrote:
> CVSROOT: /cvs/dm
> Module name: multipath-tools
> Branch: RHEL5_FC6
> Changes by: bmarzins@sourceware.org 2009-04-21 00:05:24
>
> Modified files:
> libcheckers : tur.c
> libmultipath : discovery.c discovery.h
> multipathd : main.c
> path_priority/pp_alua: rtpg.c
>
> Log message:
> Fix for bz 472451. This fixes two issues. First, it keeps multipathd from checking
> scsi paths in the "blocked" state, since multipathd will just hang until the device
> times out. Second, the tur checker retrys on a few more error codes that could happen
> during transient path failures.
>
Is there any interest having this upstream in 0.4.9, given that the
path checking method is going to be changing? I'm not sure how soon all
of those changes will be in place. Christophe, if you want me to port
this upstream, just let me know.
-Ben
next prev parent reply other threads:[~2009-04-21 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 0:05 multipath-tools libcheckers/tur.c libmultipath bmarzins
2009-04-21 17:43 ` Benjamin Marzinski [this message]
[not found] <2140769529.3263291240345156061.JavaMail.root@zimbra16-e3.priv.proxad.net>
2009-04-21 20:23 ` christophe.varoqui
-- strict thread matches above, loose matches on Subject: below --
2009-06-08 21:38 bmarzins
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=20090421174322.GV15911@ether.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=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.