Language and Page Formatting Options
4.6. The Metadata Daemon (lvmetad)
LVM can optionally use a central metadata cache, implemented through a daemon (
lvmetad) and a
udevrule. The metadata daemon has two main purposes: It improves performance of LVM commands and it allows
udevto automatically activate logical volumes or entire volume groups as they become available to the system.
lvmetaddaemon is not currently supported across the nodes of a cluster, and requires that the locking type be local file-based locking.
To take advantage of the daemon, you must do the following:
- Start the daemon through the
lvm2-lvmetadservice. To start the daemon automatically at boot time, use the
chkconfig lvm2-lvmetad oncommand. To start the daemon manually, use the
service lvm2-lvmetad startcommand.
- Configure LVM to make use of the daemon by setting the
global/use_lvmetadvariable to 1 in the
lvm.confconfiguration file. For information on the
lvm.confconfiguration file, see Appendix B, The LVM Configuration Files.
Normally, each LVM command issues a disk scan to find all relevant physical volumes and to read volume group metadata. However, if the metadata daemon is running and enabled, this expensive scan can be skipped. Instead, the
lvmetaddaemon scans each device only once, when it becomes available, by means of
udevrules. This can save a significant amount of I/O and reduce the time required to complete LVM operations, particularly on systems with many disks. For information on the
udevdevice manager and
udevrules, see Section A.3, “Device Mapper Support for the udev Device Manager”.
When a new volume group is made available at runtime (for example, through hotplug or iSCSI), its logical volumes must be activated in order to be used. When the
lvmetaddaemon is enabled, the
activation/auto_activation_volume_listoption in the
lvm.confconfiguration file can be used to configure a list of volume groups and logical volumes that should be automatically activated. Without the
lvmetaddaemon, a manual activation is necessary. By default, this list is not defined, which means that all volumes are autoactivated once all of the physical volumes are in place. The autoactivation works recursively for LVM stacked on top of other devices, as it is event-based.
lvmetaddaemon is running, the
filter =setting in the
/etc/lvm/lvm.conffile does not apply when you execute the
pvscan --cache devicecommand. To filter devices, you need to use the
global_filter =setting. Devices that fail the global filter are not opened by LVM and are never scanned. You may need to use a global filter, for example, when you use LVM devices in VMs and you do not want the contents of the devices in the VMs to be scanned by the physical host.