On Wed, 06 Mar 2013 22:41:51 +0100
Sven Arnold <sven.arn...@localite.de> wrote:
> In fact, disabling the udev rule
>
> SUBSYSTEM=="block", ACTION=="add|change",
> ENV{ID_FS_TYPE}=="lvm*|LVM*",\ RUN+="watershed sh -c '/sbin/lvm
> vgscan; /sbin/lvm vgchange -a y'"
>
> seems to resolve the problem for me.
This rule looks like asking for problems in clustered LVM environment.
It activates all volumes, non exclusively, as soon as the PV becomes
available - it leaves no place for any management by the cluster
software. I don't think this came from LVM upstream, rather it looks
like some Ubuntu invention.
Removing this rule and activating the volumes in a controlled manner
(e.g. via the LVM resource agent) seems the right way.
Greets,
Jacek
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
