From: David Teigland <teigland@sourceware.org>
To: lvm-devel@redhat.com
Subject: master - lvmlockd vdo: disallow use of shared lock on LV
Date: Tue, 29 Sep 2020 19:43:34 +0000 (GMT) [thread overview]
Message-ID: <20200929194334.B03033857C57@sourceware.org> (raw)
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=82e270c18a76d68e2efc28a194bca2e428c18fae
Commit: 82e270c18a76d68e2efc28a194bca2e428c18fae
Parent: af8044da3ab6891495f4d96b51a52bc4ae457ffb
Author: David Teigland <teigland@redhat.com>
AuthorDate: Mon Sep 28 13:48:46 2020 -0500
Committer: David Teigland <teigland@redhat.com>
CommitterDate: Tue Sep 29 14:43:26 2020 -0500
lvmlockd vdo: disallow use of shared lock on LV
vdo cannot be active on multiple hosts concurrently
---
lib/locking/lvmlockd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/locking/lvmlockd.c b/lib/locking/lvmlockd.c
index dca7954ab..9d11077e3 100644
--- a/lib/locking/lvmlockd.c
+++ b/lib/locking/lvmlockd.c
@@ -2374,6 +2374,7 @@ int lockd_lv(struct cmd_context *cmd, struct logical_volume *lv,
lv_is_thin_type(lv) ||
lv_is_mirror_type(lv) ||
lv_is_raid_type(lv) ||
+ lv_is_vdo_type(lv) ||
lv_is_cache_type(lv)) {
flags |= LDLV_MODE_NO_SH;
}
reply other threads:[~2020-09-29 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200929194334.B03033857C57@sourceware.org \
--to=teigland@sourceware.org \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.