From: Christoph Hellwig <hch@lst.de>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
Mike Snitzer <snitzer@redhat.com>,
linux-scsi@vger.kernel.org
Subject: Re: [dm-devel] [PATCH] dm-mpath: always return reservation conflict
Date: Thu, 16 Jul 2015 09:54:50 +0200 [thread overview]
Message-ID: <20150716075450.GA23334@lst.de> (raw)
In-Reply-To: <CABr-GncMR4y+Sv=cXnhbXyX+ko2d13hgsPg2xbWSp9Z-v8=nqQ@mail.gmail.com>
On Thu, Jul 16, 2015 at 05:07:03AM +0000, Christophe Varoqui wrote:
> For reference the opensvc crm does use type 5 pr, and aims for all paths
> registered. It still does not make use of the multipathd pr janitoring
> features, and uses sg_persist directly for pr status and actions.
The type doesn't matter here. It's important to set the ALL_TG_PT bit
when registering the key. As dm-mpath opens the underlying devices
exclusively, and doesn't give you a choice which path to send to you're
in a world of pain without that.
next prev parent reply other threads:[~2015-07-16 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 11:23 [PATCH] dm-mpath: always return reservation conflict Hannes Reinecke
2015-07-15 11:35 ` James Bottomley
2015-07-15 11:52 ` Hannes Reinecke
2015-07-15 11:56 ` Christoph Hellwig
2015-07-15 12:02 ` Hannes Reinecke
2015-07-15 12:01 ` James Bottomley
2015-07-15 12:15 ` Hannes Reinecke
2015-07-15 13:20 ` Mike Snitzer
2015-07-16 5:07 ` [PATCH] " Christophe Varoqui
2015-07-16 7:54 ` Christoph Hellwig [this message]
2015-07-16 14:40 ` [dm-devel] " Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2016-08-02 12:36 [PING / RESEND] handling reservation conflicts in dm-mpath Christoph Hellwig
2016-08-02 12:36 ` [PATCH] dm-mpath: always return reservation conflict Christoph Hellwig
2016-08-11 18:38 ` [dm-devel] " Christoph Hellwig
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=20150716075450.GA23334@lst.de \
--to=hch@lst.de \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@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.