If I have an LV as a backing device for a DRBD disk, can someone explain why I
need an LVM filter? It seems to me that we would want the LV to be always
active under both the primary and secondary DRBD devices, and there should be
no need or desire to have the LV activated or deactivated by
* Jean-Francois Malouin [20191029
09:49]:
> * Roger Zhou [20191029 06:18]:
> >
> > On 10/29/19 12:30 PM, Andrei Borzenkov wrote:
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Activating volume
> > >> group vg0
> > >> Oct 28 14:4
* Roger Zhou [20191029 06:18]:
>
> On 10/29/19 12:30 PM, Andrei Borzenkov wrote:
> >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Activating volume group
> >> vg0
> >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Reading all physical
> >&g
On 10/29/19 12:30 PM, Andrei Borzenkov wrote:
>> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Activating volume group vg0
>> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Reading all physical
>> volumes. This may take a while... Found volume group "vmspace" using
>> metadata type
Hi,
The command has been deprecated. It still works with the most recent pcs:
$ pcs resource show --full
Warning: This command is deprecated and will be removed. Please use 'pcs
resource config' instead.
Resource: d3 (class=ocf provider=pacemaker type=Dummy)
Operations: migrate_from
