From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] fence_scsi_test: add option for strict verification
Date: Mon, 09 Apr 2012 13:18:27 -0400 [thread overview]
Message-ID: <4F8319E3.7060101@redhat.com> (raw)
In-Reply-To: <4F82F42D.2040504@redhat.com>
On 04/09/2012 10:37 AM, Ryan O'Hara wrote:
> Add new option --strict (-s) that will enable strict verification that
> registrations are created on all paths. Previously this was the
> default behavior. Strict verification will compare the number of times
> the registration key exists on a device and the number of paths. This
> is useful when testing multipath configurations. If this option is not
> specified, the verification will simply check to make sure the
> registration keys exist on the device.
>
> Resolves: rhbz#782919
Reviewed-by: Lon Hohberger <lhh@redhat.com>
-- Lon
prev parent reply other threads:[~2012-04-09 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 14:37 [Cluster-devel] [PATCH] fence_scsi_test: add option for strict verification Ryan O'Hara
2012-04-09 17:18 ` 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=4F8319E3.7060101@redhat.com \
--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).