From: Mike Christie <mchristi@redhat.com>
To: dm-devel@redhat.com, christophe.varoqui@opensvc.com
Subject: [PATCH 0/4] multipath-tools: Ceph rbd support
Date: Tue, 5 Jul 2016 03:12:29 -0500 [thread overview]
Message-ID: <1467706353-16878-1-git-send-email-mchristi@redhat.com> (raw)
The following patches add Ceph rbd support for handling
blacklisted devices. This does not support features like
multibus.
My specific use is for exporting rbd images through multiple
LIO instances. In this case, we have one rbd instance that
has the exclusive lock and send WRITE requests. If that host
becomes unreachable, then another host will grab the lock,
and blacklist the original host to prevent it from sending stale
IO (when blacklisted IO will be failed by the OSD).
To recover from this, this patchset adds a repair() callout
to the checker. If the path is in the PATH_DOWN state this
callout can be used to fix it up. For my case, I am remapping
the device to flush stale IO and cleanup the old lock,
and then unblacklisting myself.
next reply other threads:[~2016-07-05 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 8:12 Mike Christie [this message]
2016-07-05 8:12 ` [PATCH 1/4] multipath-tools: add rbd discovery detection Mike Christie
2016-07-05 8:12 ` [PATCH 2/4] multipath-tools: add checker callout to repair path Mike Christie
2016-07-05 8:12 ` [PATCH 3/4] multipath-tools: Add rbd checker Mike Christie
2016-07-05 8:12 ` [PATCH 4/4] multipath-tools: Add rbd to the hwtable Mike Christie
2016-07-08 8:15 ` [PATCH 0/4] multipath-tools: Ceph rbd support Christophe Varoqui
2016-07-08 15:46 ` Mike Christie
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=1467706353-16878-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).