From: Mike Christie <mchristi@redhat.com>
To: dm-devel@redhat.com, christophe.varoqui@opensvc.com
Subject: [PATCH 0/5] rbd checker fixes
Date: Tue, 11 Oct 2016 16:36:50 -0500 [thread overview]
Message-ID: <1476221815-17900-1-git-send-email-mchristi@redhat.com> (raw)
The following pathces made over the multipath-tools tree today
fix some bugs in the rbd checker and sync up log messages.
The first 4 patches are a resend from here:
https://www.redhat.com/archives/dm-devel/2016-August/msg00429.html
I did not see any review comments (of course let me know if I missed
them), so the only changes are from being rebased on the current tree.
The last patch is new and adds a fix for when rbd's lock_on_read
feature is used.
next reply other threads:[~2016-10-11 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 21:36 Mike Christie [this message]
2016-10-11 21:36 ` [PATCH 1/5] rbd: fix sync repair support Mike Christie
2016-10-11 21:36 ` [PATCH 2/5] rbd: check for nonshared clients Mike Christie
2016-10-11 21:36 ` [PATCH 3/5] rbd: check for exclusive lock enabled Mike Christie
2016-10-11 21:36 ` [PATCH 4/5] rbd: fixup log messages Mike Christie
2016-10-11 21:36 ` [PATCH 5/5] rbd: use lock_on_read if set Mike Christie
2016-10-16 7:56 ` [PATCH 0/5] rbd checker fixes 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=1476221815-17900-1-git-send-email-mchristi@redhat.com \
--to=mchristi@redhat.com \
--cc=christophe.varoqui@opensvc.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.