On Thu 2015-09-17 17:33:43 +0200, Ralf Jung wrote: > Since a recent upgrade, I see the following error on every boot: > > /run/lvm/lvmetad.socket: connect failed: no such file or directory > WARNING: Failed to connect to lvmetad. Falling back to internal scanning. > > I have a LUKS-encrypted physical volume containing my root partition, and > this error > appears twice after I enter my password.
I see this on boot as well, also on systems that have the root
filesystem on an LVM volume that is only accessible once a dm-crypt
volume is unlocked.
I believe these warnings are harmless, but they are certainly noisy and
scary-looking. If that's wrong, I hope that someone more knowledgable
about LVM than i am will weigh in and explain why we should care about
this warning.
If this warning is indeed harmless, I recommend suppressing it entirely
if possible when the configuration is one one of the common ones
(e.g. in the initramfs) where we know that lvmetad is unlikely to
already be running anyway. (if detecting that state is too much
trouble, then i'd suppress it in all cases, unless the user is running
lvm with --debug or --verbose)
Regards,
--dkg
signature.asc
Description: PGP signature
