florian at hastexo
Nov 28, 2011, 12:14 PM
Post #3 of 4
On Sat, Nov 26, 2011 at 11:58 AM, Lars Marowsky-Bree <lmb [at] suse> wrote:
Re: [PATCH 2/2] Medium: LVM: force dmevent monitoring for clones
[In reply to]
> On 2011-11-25T18:38:06, Florian Haas <florian [at] hastexo> wrote:
>> Starting a clustered volume with monitoring disabled is not allowed:
>> 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:
>> Thus, for cloned instances, always invoke vgchange with "--monitor y".
>> Thanks to Nils Meyer <nils [at] nm> 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 ...?
Surely you're joking. resource-agents does not enforce any packaging
dependencies for the stuff it's capable of managing, so why throw in a
random conflict here?
Of course, we probably wouldn't have this version issue if the LVM RA
was packaged with LVM, but someone shot down that suggestion. Who was
that, I wonder? I'm thinking, I'm thinking... nevermind, it'll come to
Linux-HA-Dev: Linux-HA-Dev [at] lists
Home Page: http://linux-ha.org/