From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] fence_scsi: identify dm-multipath devices correctly
Date: Tue, 18 Jan 2011 20:25:17 -0500 [thread overview]
Message-ID: <1295400317.2696.292.camel@localhost.localdomain> (raw)
In-Reply-To: <1295383323-6548-1-git-send-email-rohara@redhat.com>
On Tue, 2011-01-18 at 14:42 -0600, Ryan O'Hara wrote:
> Previously, fence_scsi would only identify /dev/dm* devices as being
> multipath devices. This prevented the use of "friendly" dm-multipath
> names (eg. /dev/mapper/mpath1). Since fence_scsi can now be passed
> devices to operate on, it should be able to handle "friendly" names,
> too. This patch fixes the problem by getting the absolute path of the
> device at registration time.
>
> Resolves: rhbz#644389
>
> Signed-off-by: Ryan O'Hara <rohara@redhat.com>
> ---
> fence/agents/scsi/fence_scsi.pl | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/fence/agents/scsi/fence_scsi.pl b/fence/agents/scsi/fence_scsi.pl
> index 9ee8917..8ddde4e 100644
> --- a/fence/agents/scsi/fence_scsi.pl
> +++ b/fence/agents/scsi/fence_scsi.pl
> @@ -1,5 +1,6 @@
> #!/usr/bin/perl
>
> +use Cwd 'realpath';
> use File::Basename;
> use Getopt::Std;
> use POSIX;
> @@ -112,6 +113,8 @@ sub do_register ($$$)
> my $self = (caller(0))[3];
> my ($host_key, $node_key, $dev) = @_;
>
> + $dev = realpath ($dev);
> +
> if (substr ($dev, 5) =~ /^dm/) {
> my @slaves = get_mpath_slaves ($dev);
> foreach (@slaves) {
> @@ -139,6 +142,8 @@ sub do_register_ignore ($$)
> my $self = (caller(0))[3];
> my ($node_key, $dev) = @_;
>
> + $dev = realpath ($dev);
> +
> if (substr ($dev, 5) =~ /^dm/) {
> my @slaves = get_mpath_slaves ($dev);
> foreach (@slaves) {
ACK; this is fine
-- Lon
prev parent reply other threads:[~2011-01-19 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 20:42 [Cluster-devel] [PATCH] fence_scsi: identify dm-multipath devices correctly Ryan O'Hara
2011-01-19 1:25 ` Lon Hohberger [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=1295400317.2696.292.camel@localhost.localdomain \
--to=lhh@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).