On the other-hand not many people have clustered vgs setup, and if they do we can require dmeventd running.
Thus i'll propose a patch for precise to read monitoring value from /etc/lvm/lvm.conf if vg_is_clustered are detected.
I'll first test these assumptions with juju using precise machines to make sure it solves this bug and doesn't change lvm behaviour for non-clustered case.
I disagree with the proposed fix in https:/ /bugs.launchpad .net/ubuntu/ +source/ lvm2/+bug/ 833368/ comments/ 46 /bugs.launchpad .net/ubuntu/ +source/ lvm2/+bug/ 833368/ comments/ 11
Due to the reason behind this patch - https:/
On the other-hand not many people have clustered vgs setup, and if they do we can require dmeventd running.
Thus i'll propose a patch for precise to read monitoring value from /etc/lvm/lvm.conf if vg_is_clustered are detected.
I'll first test these assumptions with juju using precise machines to make sure it solves this bug and doesn't change lvm behaviour for non-clustered case.
Regards,
Dmitrijs.