From: Christoph Hellwig <hch@lst.de>
To: dm-devel@redhat.com, linux-scsi@vger.kernel.org
Cc: hare@suse.com
Subject: [PING / RESEND] handling reservation conflicts in dm-mpath
Date: Tue, 2 Aug 2016 14:36:31 +0200 [thread overview]
Message-ID: <1470141392-25479-1-git-send-email-hch@lst.de> (raw)
Hannes sent this patch a bit more than a year ago, but it got silently
dropped. When using the pNFS SCSI layout we can easily hit a
failover "livelock" without it as the reservation conflicts on a
newly detected device that doesn't have layouts yet, or after a fency
will keep failing over from one path to another for no reason at all.
Any chance to get it into mainline now?
next reply other threads:[~2016-08-02 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:36 Christoph Hellwig [this message]
2016-08-02 12:36 ` [PATCH] dm-mpath: always return reservation conflict Christoph Hellwig
2016-08-11 18:38 ` [dm-devel] " Christoph Hellwig
2016-08-15 13:08 ` Mike Snitzer
2016-08-15 13:40 ` Mike Snitzer
2016-09-26 16:52 ` [dm-devel] " Christoph Hellwig
2016-09-26 19:06 ` James Bottomley
2016-09-27 6:34 ` Hannes Reinecke
2016-09-27 18:50 ` James Bottomley
2016-09-29 15:01 ` Mike Snitzer
2016-09-29 15:35 ` Christoph Hellwig
2016-09-30 0:55 ` James Bottomley
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=1470141392-25479-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=dm-devel@redhat.com \
--cc=hare@suse.com \
--cc=linux-scsi@vger.kernel.org \
/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).