From 7f7ec769d98cfe7af47b202189b279f354763b5a Mon Sep 17 00:00:00 2001 From: David Teigland Date: Thu, 24 May 2018 11:41:14 -0500 Subject: lvmlockd: do not use an LV lock for some lvchange options Some lvchange options can be used even if the LV is active. --- tools/lvchange.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'tools/lvchange.c') diff --git a/tools/lvchange.c b/tools/lvchange.c index 0aac5ac19..6144852b6 100644 --- a/tools/lvchange.c +++ b/tools/lvchange.c @@ -1056,9 +1056,11 @@ static int _lvchange_properties_single(struct cmd_context *cmd, int i, opt_enum; uint32_t mr = 0; - /* If LV is inactive here, ensure it's not active elsewhere. */ - if (!lockd_lv(cmd, lv, "ex", 0)) - return_ECMD_FAILED; + /* + * We do not acquire an lvmlockd lock on the LV here because these are + * VG metadata changes that do not conflict with the LV being active on + * another host. + */ /* First group of options which allow for one metadata commit/update for the whole group */ for (i = 0; i < cmd->command->ro_count; i++) { -- cgit v1.2.1