On 2011-11-25T18:38:06, Florian Haas <[email protected]> wrote:
> Starting a clustered volume with monitoring disabled is not allowed:
>
> http://www.redhat.com/archives/lvm-devel/2010-March/msg00289.html
>
> Which would be fine, as activation/monitoring = 1 ships as the default
> in lvm.conf. However, at least some versions of LVM seem to ignore this,
> throwing an error on vgchange unless "--monitor y" is explicitly set
> on the command line:
>
> https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368
>
> Thus, for cloned instances, always invoke vgchange with "--monitor y".
>
> Thanks to Nils Meyer <[email protected]> for pointing out this issue.
> ---
> heartbeat/LVM | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
Seems to make sense. of course, an alternative would be to add a
"Conflicts: lvm2 < x.y.z" to the package on the respective versions to
make sure it's only installed with a fixed lvm2 package ...?
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
