On Sun, 23 Dec 2018 15:36:25 +0100 Xavier Guerrin <xav...@kindwolf.org>
wrote:
I investigated why and what follows are my strace-based conclusions.
As you probably know already, lvm2-activation-generator runs:
/sbin/lvmconfig global/event_activation global/use_lvmpolld
After the latest lvm2 upgrade, it turns out /etc/lvm/lvm.conf does *not* contain
event_activation in its global section.
Therefore, lvmconfig:
- outputs "Configuration node global/event_activation not found" on stderr;
- outputs "use_lvmpolld=1" on stdout;
- exits with return code 1, hence the reported error.
Excellent bug report Xavier! It was really helpful for me.
I can confirm that setting "event_activation=1" solves all these
"lvm2-activation-generator: lvmconfig failed" messages.
That option is missing from the Debian setup but is present and enabled
upstream, as showed by this command:
lvmconfig --typeconfig default --withcomments
Cesare.
