From: Mike Snitzer <snitzer@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: dm-devel@redhat.com, Sean Stewart <sean.stewart@netapp.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: dm-multipath: Accept failed paths for multipath maps
Date: Wed, 18 Dec 2013 09:08:58 -0500 [thread overview]
Message-ID: <20131218140858.GC17730@redhat.com> (raw)
In-Reply-To: <1387353155-7271-1-git-send-email-hare@suse.de>
On Wed, Dec 18 2013 at 2:52am -0500,
Hannes Reinecke <hare@suse.de> wrote:
> The multipath kernel module is rejecting any map with an invalid
> device. However, as the multipathd is processing the events serially
> it will try to push a map with invalid devices if more than one
> device failed at the same time.
> So we can as well accept those maps and make sure to mark the
> paths as down.
Why is it so desirable to do this? Reduced latency to restore at least
one valid path when a bunch of paths go down?
Why can't we just rely on userspace eventually figuring out which paths
are failed and pushing a valid map down?
Are there favorable reports that this new behavior actually helps?
Please quantify how.
(As an aside, really not a fan of parse_path doing what you've
suggested.. will look closer once I have more justification to do so)
next prev parent reply other threads:[~2013-12-18 14:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 7:52 [PATCHv2] dm-multipath: Accept failed paths for multipath maps Hannes Reinecke
2013-12-18 14:08 ` Mike Snitzer [this message]
2013-12-18 14:25 ` Hannes Reinecke
2013-12-18 15:28 ` Stewart, Sean
2013-12-19 8:21 ` Bart Van Assche
2014-02-19 1:14 ` Mike Snitzer
2014-02-19 8:11 ` Bart Van Assche
2014-07-18 0:04 ` Mike Snitzer
2014-07-18 0:23 ` Mike Snitzer
2014-07-18 6:00 ` Hannes Reinecke
2014-07-18 16:04 ` Mike Snitzer
2014-07-18 16:15 ` Mike Snitzer
2014-07-21 6:05 ` Hannes Reinecke
2014-07-18 0:29 ` John Utz
2014-07-18 2:18 ` Mike Snitzer
2014-07-18 3:31 ` John Utz
2014-07-18 5:57 ` Hannes Reinecke
2014-07-18 14:38 ` Mike Snitzer
2014-07-18 17:04 ` John Utz
2014-07-21 14:23 ` ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps) Hannes Reinecke
2014-07-21 19:28 ` Kent Overstreet
2014-07-22 5:46 ` Hannes Reinecke
2014-07-22 8:08 ` Matias Bjorling
2014-07-18 16:51 ` dm-multipath: Accept failed paths for multipath maps John Utz
2014-07-18 6:12 ` Hannes Reinecke
2013-12-18 15:28 ` Merla, ShivaKrishna
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=20131218140858.GC17730@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=sean.stewart@netapp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox