>> During the reboot of a server many distributions do a "vgscan --mknodes",
>> which will activate the VG.
>Pacemaker checks on startup for all resources on a node if
>they're running (started).
Yes, that is true. But as mentioned above a vgscan during the boot will
activate the VG, which many
On Wed, Apr 27, 2011 at 09:40:22AM +0200, Ulf wrote:
> Hi,
> I'm not sure if inux-ha-...@lists.linux-ha.org will receive this message, as
> I'm not subscribed to.
It won't, you need to subscribe.
> >Can you please elaborate on the benefits this patch would bring.
> >Is it supposed to prevent a V
Hi,
I'm not sure if inux-ha-...@lists.linux-ha.org will receive this message, as
I'm not subscribed to.
>Can you please elaborate on the benefits this patch would bring.
>Is it supposed to prevent a VG from being mounted on more than
>one node?
Following scenario: Shared storage with a VG and a
Hi,
On Tue, Apr 19, 2011 at 03:56:16PM +0200, Ulf wrote:
> Hi,
>
> I attached a patch to enhance the LVM agent with the capability to set a tag
> on the VG (set_hosttag = true) in conjunction with a volume_list filter this
> can prevent to activate a VG on multiple host. Unfortunately active VG
Hi,
I attached a patch to enhance the LVM agent with the capability to set a tag on
the VG (set_hosttag = true) in conjunction with a volume_list filter this can
prevent to activate a VG on multiple host. Unfortunately active VGs will stay
active in case of unclean operation.
The tag is always
