linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Gang He <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] discussion about activation/auto_activation_volume_list
Date: Thu, 19 Nov 2020 10:56:15 +0800	[thread overview]
Message-ID: <caf2d160-aa4f-6598-6199-e7727100f87a@suse.com> (raw)
In-Reply-To: <20201118182300.GB28264@redhat.com>

Hi David,

On 2020/11/19 2:23, 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:
> https://bugzilla.redhat.com/show_bug.cgi?id=1899214
Thank for your follow-up.
More comments here,
Should we keep the default behavior like before? e.g. VG/LV should be 
auto-activated by default like before.Otherwise, some users will feel
strange after lvm upgrade.

Second, how to keep the compatibility with the existed VG/LV? since we 
can upgrade lvm2 version, but VG/LV is possible old. I wonder if there 
are some Reserved Bits in lvm meta-data layout to use? if yes, I feel 
this proposal is very perfect.

Thanks
Gang

> 
> Dave
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

  reply	other threads:[~2020-11-19  2:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  8:00 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 [this message]
2020-11-19  6:46       ` heming.zhao
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:
  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=caf2d160-aa4f-6598-6199-e7727100f87a@suse.com \
    --to=ghe@suse.com \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] discussion about activation/auto_activation_volume_list' \
    /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

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