From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: fedora/rh: is hp_tur checker still needed?
Date: Wed, 24 Aug 2016 23:01:32 -0500 [thread overview]
Message-ID: <20160825040132.GW26062@octiron.msp.redhat.com> (raw)
In-Reply-To: <859fb60d-10ee-00e8-b4d9-53ff237c2336@gmail.com>
On Wed, Aug 17, 2016 at 03:12:21PM +0200, Xose Vazquez Perez wrote:
> Hi Benjamin,
>
> Doc says:
> On some storage devices, if a LUN is deleted from an existing multipathd
> device, and a new LUN is presented to the host, it may end up with the
> same LUN ID and name as the old LUN. In this case, multipath will assume
> that this is the old LUN and belongs to the existing multipath device.
> This cause cause corruption. A new path checker "hp_tur" has been added
> that verifies the WWID of the LUN when it checks the path, to avoid this
> problem.
> Code: http://pkgs.fedoraproject.org/cgit/rpms/device-mapper-multipath.git/plain/0007-RH-add-hp_tur-checker.patch
No. Nothing has used it for a while.
-Ben
prev parent reply other threads:[~2016-08-25 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 13:12 fedora/rh: is hp_tur checker still needed? Xose Vazquez Perez
2016-08-25 4:01 ` Benjamin Marzinski [this message]
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=20160825040132.GW26062@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=xose.vazquez@gmail.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).