Re: [linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-19 Thread heming.z...@suse.com
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 clust

Re: [linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-18 Thread Gang He
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 clu

Re: [linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-18 Thread heming.z...@suse.com
On 11/18/20 12:17 AM, David Teigland wrote: > On Tue, Nov 17, 2020 at 04:00:10PM +0800, heming.z...@suse.com wrote: >> Hello LVM-maintainers, >> >> Currently activation/auto_activation_volume_list is not enable and it does >> the default behavior: >>pvscan will activate all the devices on boot

Re: [linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-18 Thread David Teigland
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

Re: [linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-17 Thread Gang He
On 11/18/2020 12:17 AM, David Teigland wrote: On Tue, Nov 17, 2020 at 04:00:10PM +0800, heming.z...@suse.com wrote: Hello LVM-maintainers, Currently activation/auto_activation_volume_list is not enable and it does the default behavior: pvscan will activate all the devices on booting. Th

Re: [linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-17 Thread David Teigland
On Tue, Nov 17, 2020 at 04:00:10PM +0800, heming.z...@suse.com wrote: > Hello LVM-maintainers, > > Currently activation/auto_activation_volume_list is not enable and it does > the default behavior: > pvscan will activate all the devices on booting. > > This rule will trigger a clumsy process i

[linux-lvm] discussion about activation/auto_activation_volume_list

2020-11-17 Thread heming.z...@suse.com
Hello LVM-maintainers, Currently activation/auto_activation_volume_list is not enable and it does the default behavior: pvscan will activate all the devices on booting. This rule will trigger a clumsy process in HA (corosync+pacemaker stack) env. ## let me show the scenario: 2 nodes (A & B)