Updated: 28 September 2026 · Applies to: LVM 2.03 on AlmaLinux and Rocky Linux 9 and 10, RHEL 9 and 10, Ubuntu 24.04 and 26.04, Debian 13
On CentOS 7 and similar older systems, the lvmetad daemon cached LVM metadata, and guides often told you to disable it (use_lvmetad = 0 in lvm.conf) for clusters, multipath or troubleshooting. lvmetad no longer exists: it was removed in LVM 2.03, the version in every current distribution. On AlmaLinux 9 with LVM 2.03.33, lvmconfig global/use_lvmetad answers "Configuration node global/use_lvmetad not found", and there is no lvmetad service. There is nothing to disable.
What replaced it
- Event-based activation: when a disk appears, udev runs
pvscanand LVM activates the volume group once all its physical volumes are present. This is controlled byevent_activationin theglobalsection of/etc/lvm/lvm.conf(default 1, on). - The devices file (AlmaLinux, Rocky Linux and RHEL 9 and 10): LVM only uses the disks listed in
/etc/lvm/devices/system.devices. This does what filters and lvmetad were often used for: keeping LVM away from disks it should not touch, such as multipath paths or disks belonging to virtual machines.
Common tasks today
lvmdevices # disks LVM is allowed to use lvmdevices --adddev /dev/sdc # allow a new disk lvmdevices --deldev /dev/sdc # stop using a disk pvscan --cache # rescan all devices
Switch off automatic activation
If you disabled lvmetad to stop volume groups from being activated automatically (for example shared storage in a cluster), use these settings instead:
- Per volume group:
vgchange --setautoactivation n vgname - For the whole system:
event_activation = 0inlvm.conf, so that volume groups are only activated at boot and by hand.
Old settings in lvm.conf
If an old lvm.conf still contains use_lvmetad, current LVM simply ignores it (we checked this with LVM 2.03.33). Remove the line to avoid confusion; it has no effect.
Official documentation: lvmdevices manual page and lvmautoactivation manual page.