LVM in boot process

English Install/Boot/Login
#1

Hi folks, I was having a look at my logs and found that during boot, the system scans for LVM’s. I don’t use them. Can I stop this service from running?

This is the relevant part of the bootlog:

linux:~ # cat /var/log/boot.log |grep LVM
OK ] Listening on LVM2 metadata daemon socket.
Starting LVM2 metadata daemon…
OK ] Started LVM2 metadata daemon.
Starting Activation of LVM2 logical volumes…
OK ] Started Activation of LVM2 logical volumes.
Starting Activation of LVM2 logical volumes…
OK ] Started Activation of LVM2 logical volumes.
Starting Activation of LVM2 logical volumes…
OK ] Started Activation of LVM2 logical volumes.
Starting Activation of LVM2 logical volumes…
OK ] Started Activation of LVM2 logical volumes.

(I found this thread, but it looks like the op lost interest…
https://forums.opensuse.org/showthread.php/494300-lvm2-is-stopping-the-boot-process/page2)

#2

Is there a reason you want to stop it?? Is it taking a long time? DO a

systemd-analyze blame

to see how long that really takes

#3

Yes…! That is over thirty milliseconds out of my busy life every time I boot up! :O>:(:open_mouth:


            65ms *lvm2-activation-early.service*
            62ms iscsi.service
            61ms vboxautostart-service.service
            58ms cycle.service
            52ms udisks2.service
            51ms user@1000.service
            49ms systemd-fsck-root.service
            43ms systemd-udev-root-symlink.service
            34ms systemd-modules-load.service
            34ms plymouth-read-write.service
            33ms dev-hugepages.mount
            33ms systemd-fsck@dev-disk-by\x2duuid-79567642\x2d12c5\x2d40c8\x2d8e98\x2d9091ccef57e0.service
            33ms *lvm2-activation.service*
            32ms systemd-udev-trigger.service
            32ms systemd-journal-flush.service
            31ms kmod-static-nodes.service
            31ms sys-kernel-debug.mount
            29ms *lvm2-lvmetad.service*
            28ms dev-mqueue.mount
            27ms auditd.service
            27ms dm-event.service
            26ms systemd-tmpfiles-setup.service
            22ms Store.mount

I had no real reason to want to stop them, it is just having stuff which is never used is just one more thing to go wrong, and having spotted them there I wished to know how to stop them if they did ever start to misbehave, on another system for instance.

#4

If it ain’t broke don’t fix it. :wink:

It is just checking to see if maybe you added a LVM no big deal

#5

It took me quite a long time to run that systemd command. Far longer than the services will ever take in a lifetime of boot-ups. The reason? I am an idiot. And English. So I tried:

systemd-analyse blame
systemd-analyse-blame
systemd analyse-blame
zypper in systemd-analyse
YASt search systemd-analyse

etc etc. Then I realised that systemd has chosen the US spelling “analyze”
D’oh!
http://gamemes.com/store/131226/10338_v0_610x.jpg