archive mirror
 help / color / mirror / Atom feed
From: "" <>
To: LVM general discussion and development <>,
	David Teigland <>
Subject: Re: [linux-lvm] discussion about activation/auto_activation_volume_list
Date: Thu, 19 Nov 2020 14:46:15 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/19/20 2:23 AM, David Teigland wrote:
> On Wed, Nov 18, 2020 at 09:28:21AM +0800, Gang He wrote:
>> I prefer to use a metadata flag for each VG or LV to skip auto-activation.
>> Otherwise, it is not easy for the pacemaker cluster to manager a local
>> VG(e.g. local or systemid type) in a cluster via active-passive mode.
> I created a bug for this:

Hello Dave

I read the bug ticket and verified the "lvchange -k", it works.
If I understand correctly, the "lvchange -k" is enough for current issue. 
And you previous mails wanted to have a new function/flag for unify management vg & lv, am I right?

  parent reply	other threads:[~2020-11-19  6:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  8:00 [linux-lvm] discussion about activation/auto_activation_volume_list heming.zhao
2020-11-17 16:17 ` David Teigland
2020-11-18  1:28   ` Gang He
2020-11-18 18:23     ` David Teigland
2020-11-19  2:56       ` Gang He
2020-11-19  6:46       ` heming.zhao [this message]
2020-11-18 15:38   ` heming.zhao

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).