Upstream clearly states that if lvmetad is run only if "use_lvmetad" is enabled in lvm.conf, but for default it's not, so lvmetad shouldn't be started by default. "use_lvmetad" is well described in comments, so if user enables it he/she is well informed that he/she should rc-update-add lvmetad, too. Reproducible: Always
*** This bug has been marked as a duplicate of bug 500732 ***
Jeroen, please re-open this bug. It is not a duplicate of bug 500732. Both Amadeusz and El Goretto are correct. lvmetad is not a hard requirement, yet Gentoo currently depends on it in the lvm runscript. Worse, Gentoo's default lvm.conf specifies "use_lvmetad = 0". This combination is wrong and causes the various userspace tools to print this warning: WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! This warning is a serious matter. If the user decides to define "use_lvmetad = 1" - an ostensibly reasonable course of action given that Gentoo forcibly starts lvmetad - but neglects to restart lvmetad prior to this change, it may be that corruption can occur: https://bugzilla.redhat.com/show_bug.cgi?id=837603 In summary: * lvmetad is optional * Gentoo should, in turn, allow for lvmetad to be optional Were it not for the above warning, I would have suggested a revision bump to change the default value of use_lvmetad until the above two points are hammered out. Clearly, that's not an option.
*** This bug has been marked as a duplicate of bug 525614 ***
Thanks for the report. Fixed in http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef66b97c3c1778c3c8e9f96d80057ad7a1a3e2f4
