From: Eric Ren <zren@suse.com>
To: David Teigland <teigland@redhat.com>
Cc: roger zhou <zzhou@suse.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] lvmlockd manpage: prevent concurrent activation of logical volumes?
Date: Thu, 28 Dec 2017 16:30:09 +0800 [thread overview]
Message-ID: <4c07ee03-0ff8-9d41-ef93-c47e5325bb1c@suse.com> (raw)
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?
What I interpret from it is:
with clvmd, 'vgchange/lvchange -ay' activates the LV on every node in a
shot.
But with lvmlockd, one needs to perform:
- start the lockspace
vgchange --lockstart vg1
- vgchange -ay vg1
The LVs in vg1 will only be activated on this node.
Regards,
Eric
next reply other threads:[~2017-12-28 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 8:30 Eric Ren [this message]
2018-01-02 16:15 ` [linux-lvm] lvmlockd manpage: prevent concurrent activation of logical volumes? David Teigland
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=4c07ee03-0ff8-9d41-ef93-c47e5325bb1c@suse.com \
--to=zren@suse.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@redhat.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).