Re: [Linux-ha-dev] [PATCH 2/2] Medium: LVM: force dmevent monitoring for clones

2011-11-30 Thread Lars Marowsky-Bree
On 2011-11-28T21:14:22, Florian Haas wrote: > > 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 ...? > Surely you're joking. resource-agents does

Re: [Linux-ha-dev] [PATCH 2/2] Medium: LVM: force dmevent monitoring for clones

2011-11-28 Thread Florian Haas
On Sat, Nov 26, 2011 at 11:58 AM, Lars Marowsky-Bree wrote: > On 2011-11-25T18:38:06, Florian Haas 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/moni

Re: [Linux-ha-dev] [PATCH 2/2] Medium: LVM: force dmevent monitoring for clones

2011-11-26 Thread Lars Marowsky-Bree
On 2011-11-25T18:38:06, Florian Haas 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 so

[Linux-ha-dev] [PATCH 2/2] Medium: LVM: force dmevent monitoring for clones

2011-11-25 Thread Florian Haas
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