Why are LVM services/units starting by default when I don't need them?

TheDcoder · 2020-10-23 18:26:41

Hi,

I recently used systemd-analyse plot to see my boot "diagram" and I noticed that there are several "lvm" units which are being loaded by default, I never used LVM on my computer.

According to pacman, the lvm2 package was installed as a (deep) dependency for Gnome Disks which I use occasionally. I am okay with it being installed, but how do I disable it from automatically starting? Usually services in Arch are disabled until they are explicitly enabled by the user. I tried to disable them manually (both the .service and .socket units) but they are still starting for some reason

What should I do to disable them? And optionally, can I remove the lvm2 package and substitute with some dummy package or something like that?

eschwartz · 2020-10-23 19:03:50

"systemctl mask foo.service foo.socket" to prevent them from ever being activated for any reason.

Note the package is one of the rare ones activated in the package, which provides:

/usr/lib/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket
/usr/lib/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket
/usr/lib/systemd/system/sysinit.target.wants/lvm2-monitor.service

I presume the idea is bad things can happen if core system infra for mounting disks simply fails.

I have these masked too...

TheDcoder · 2020-10-23 19:12:57

Thanks for the hint! I have masked those default units and hopefully they won't start in the next boot

Note the package is one of the rare ones activated in the package, which provides:

Yes, I did notice that, and found it very strange

Maybe we should open a ticket to change this behavior? This goes against what Arch usually does, and stands for... i.e total user control of their software.

Trilby · 2020-10-23 20:47:57

I can't find references at the moment, but I do know this has come up a couple times before. While I'd personally completely agree with you, when it previously came up it seemed that the relevant dev(s) were not convinced. It's not any sort of oversight, it was a deliberate and considered choice - so simply opening a ticket to ask the dev(s) to reconsider may not be productive if there is no new information or relevant changes to the package / services in the intervening time.

Last edited by Trilby (2020-10-23 20:48:19)

loqs · 2020-10-23 20:51:25

https://bugs.archlinux.org/task/50420

TheDcoder · 2020-10-23 22:19:24

You are right Trilby, since they have already made a decision, a new ticket with nothing new wouldn't be very productive... Thanks to loqs for mentioning the ticket. Good to know that it was deliberate and not some old mistake left-out for backwards compatibility!

Arch Linux

#1 2020-10-23 18:26:41

Why are LVM services/units starting by default when I don't need them?

#2 2020-10-23 19:03:50

Re: Why are LVM services/units starting by default when I don't need them?

#3 2020-10-23 19:12:57

Re: Why are LVM services/units starting by default when I don't need them?

#4 2020-10-23 20:47:57

Re: Why are LVM services/units starting by default when I don't need them?

#5 2020-10-23 20:51:25

Re: Why are LVM services/units starting by default when I don't need them?

#6 2020-10-23 22:19:24

Re: Why are LVM services/units starting by default when I don't need them?

Board footer