Linux Device Mapper development
 help / color / mirror / Atom feed
From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: [PATCH v3 0/7] misc patches
Date: Tue, 14 Feb 2017 20:16:50 -0600	[thread overview]
Message-ID: <1487125017-22049-1-git-send-email-bmarzins@redhat.com> (raw)

Here's a couple of minor features bugfixes and cleanups. The biggest
change is that the detect_checker option now sets the checker for
devices with detected ALUA to TUR. Also, udev wasn't correctly
disabling rules for multipath devices that lost their last usable
path through a table reload. This was causing lvmetad some problems
on failing multipath devices.

Differences from v2:

libmultipath: add detect_checker option
----------------------------------------
I've removed is_alua, and now just use the paths tpgs variable to
check if the path is in ALUA mode.

Benjamin Marzinski (7):
  kpartx: don't keep creating recursive partitions
  libmultipath: add detect_checker option
  libmultipath: cleanup orphan device states
  multipathd: don't update priority of failed paths
  multipathd: add messages on delayed path addition
  multipathd: allow resetting stats
  fix udev rules for failed multipath devices

 kpartx/dos.c                          |  2 +-
 libmultipath/config.c                 |  3 ++
 libmultipath/config.h                 |  2 ++
 libmultipath/defaults.h               |  1 +
 libmultipath/devmapper.c              |  3 +-
 libmultipath/devmapper.h              |  6 ++++
 libmultipath/dict.c                   | 10 ++++++
 libmultipath/discovery.c              | 28 +++++++++++++--
 libmultipath/hwtable.c                |  1 +
 libmultipath/print.c                  |  4 +--
 libmultipath/prioritizers/alua_spc3.h |  1 +
 libmultipath/propsel.c                | 31 ++++++++++------
 libmultipath/propsel.h                |  1 +
 libmultipath/structs.c                |  2 ++
 libmultipath/structs.h                |  7 ++++
 multipath/11-dm-mpath.rules           | 67 ++++++++++++++++++++++++-----------
 multipath/multipath.conf.5            | 18 ++++++++++
 multipathd/cli.c                      |  2 ++
 multipathd/cli_handlers.c             | 44 +++++++++++++++++++++++
 multipathd/cli_handlers.h             |  2 ++
 multipathd/main.c                     |  8 ++++-
 21 files changed, 206 insertions(+), 37 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2017-02-15  2:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  2:16 Benjamin Marzinski [this message]
2017-02-15  2:16 ` [PATCH v3 1/7] kpartx: don't keep creating recursive partitions Benjamin Marzinski
2017-02-27  6:03   ` Christophe Varoqui
2017-02-15  2:16 ` [PATCH v3 2/7] libmultipath: add detect_checker option Benjamin Marzinski
2017-02-20 11:38   ` Martin Wilck
2017-02-15  2:16 ` [PATCH v3 3/7] libmultipath: cleanup orphan device states Benjamin Marzinski
2017-02-15  2:16 ` [PATCH v3 4/7] multipathd: don't update priority of failed paths Benjamin Marzinski
2017-02-15  2:16 ` [PATCH v3 5/7] multipathd: add messages on delayed path addition Benjamin Marzinski
2017-02-15  2:16 ` [PATCH v3 6/7] multipathd: allow resetting stats Benjamin Marzinski
2017-02-15  2:16 ` [PATCH v3 7/7] fix udev rules for failed multipath devices Benjamin Marzinski
2017-02-27  6:09 ` [PATCH v3 0/7] misc patches 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=1487125017-22049-1-git-send-email-bmarzins@redhat.com \
    --to=bmarzins@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox