From: David Teigland <teigland@redhat.com>
To: Eric Ren <zren@suse.com>
Cc: roger zhou <zzhou@suse.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvmlockd manpage: prevent concurrent activation of logical volumes?
Date: Tue, 2 Jan 2018 10:15:39 -0600 [thread overview]
Message-ID: <20180102161539.GB26695@redhat.com> (raw)
In-Reply-To: <4c07ee03-0ff8-9d41-ef93-c47e5325bb1c@suse.com>
On Thu, Dec 28, 2017 at 04:30:09PM +0800, Eric Ren wrote:
> Hi David,
>
> I's afraid the statement below in description section of lvmlockd manpage:
>
> "
> � prevent concurrent activation of logical volumes
> "
>
> is easy for normal user to mistake it as: wow, lvmlockd doesn't support
> active-active LV on multiple nodes?
Hi, I see what you mean. What that point was trying to summarize is
"prevent conflicting activation of LVs". I may just make that one
word change.
Thanks
prev parent reply other threads:[~2018-01-02 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 8:30 [linux-lvm] lvmlockd manpage: prevent concurrent activation of logical volumes? Eric Ren
2018-01-02 16:15 ` David Teigland [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=20180102161539.GB26695@redhat.com \
--to=teigland@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=zren@suse.com \
--cc=zzhou@suse.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).