[dm-devel] dm-multipath: Accept failed paths for multipath maps
snitzer at redhat.com
Fri Jul 18 16:04:49 UTC 2014
On Fri, Jul 18 2014 at 2:00am -0400,
Hannes Reinecke <hare at suse.de> wrote:
> On 07/18/2014 02:23 AM, Mike Snitzer wrote:
> >On Thu, Jul 17 2014 at 8:04pm -0400,
> >Mike Snitzer <snitzer at redhat.com> wrote:
> >>Revisiting this can of worms...
> >>As part of full due-diligence on the approach that SUSE and NetApp have
> >>seemingly enjoyed "for years" I reviewed Hannes' v3 patch, fixed one
> >>issue and did some cleanup. I then converted over to using a slightly
> >>different approach where-in the DM core becomes a more willing
> >>co-conspirator in this hack by introducing the ability to have
> >>place-holder devices (dm_dev without an opened bdev) referenced in a DM
> >>table. The work is here:
> >Here is the rolled up patch (the individual commits in the above branch
> >are rather noisy given the sequencing):
> > drivers/md/dm-mpath.c | 51 +++++++++++++++++++++++++++++++++----------------
> > drivers/md/dm-table.c | 53 ++++++++++++++++++++++++++++++++++++++-------------
> > drivers/md/dm.c | 5 ++---
> > drivers/md/dm.h | 12 ++++++++++++
> > 4 files changed, 89 insertions(+), 32 deletions(-)
> These patches look quite okay; I'll be cross-checking with my
> version and do some testing there.
Thanks, the intent was to make your approach more "official". I did
have a couple fixes to the DM core patch so I rebased, see:
But as I said in earlier posts, I'm really not in love with using
place-holder devices (mainly because allowing references to dead devices
_seems_ to go against proper device stacking). But I do think that DM
core _should_ acknowledge that everything isn't always going to be
perfect for all targets. Especially a target like multipath whose
purpose is to cope with the potential for paths coming/going.
So there definitely is a case to be made for DM being more tolerate of
the potential for devices being inaccessible.
Now this is the last I'm going to channel Alasdair's argument for him on
this thread but: Alasdair would prefer to see userspace multipathd fixed
(more intelligent batched processing of uevents, etc). As a second
option, his preferred kernel change is a "handover" style approach that
hands the path group state over from the old table to the new.
I agree that userspace multipathd should be fixed to process events in
batches but I see that even then the kernel should accommodate potential
for imperfect table loads for targets like multipath. I happen to
disagree with handover (I flipped and now flopped back on this point).
Handover would be serious churn (that agk somehow thinks more
worthwhile). While I appreciate that mechanically handover is a
different means to the same end of having references to dm_devs that are
"removed failed devices" handover would be overly complicated and
brittle (and very disruptive to DM core because the dm_devs aren't
hanging directly off of a multipath structure, they are associated with
the DM table!)
In that light I do actually prefer the blunt/simple approach taken in my
'throwaway-dm-mpath-placeholder-devs' branch. But I'm concerned that
accepting a workaround like this will just enable multipathd to never
get the attention it needs for improved uevent processing. If others
commit to actually making multipathd's uevent processing better that'd
go a long way.
> Will be sending some update once the testing is done.
OK. The stronger case that can be made for the stability of this change
(no missing checks for dev->bdev, etc) the better.
I did just do some basic testing, of both dm-mpath and dm-thinp, seems
fine. The DM core changes really are simple (just some extra negative
checks that won't ever apply for the normal case -- where "normal case"
is DM targets that use dm_get_device rather than __dm_get_device, and
had to add a dev_t to struct dm_dev).
More information about the dm-devel