mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
116aa71d50
The LVM devices file lists devices that lvm can use. The default
file is /etc/lvm/devices/system.devices, and the lvmdevices(8)
command is used to add or remove device entries. If the file
does not exist, or if lvm.conf includes use_devicesfile=0, then
lvm will not use a devices file. When the devices file is in use,
the regex filter is not used, and the filter settings in lvm.conf
or on the command line are ignored.
LVM records devices in the devices file using hardware-specific
IDs, such as the WWID, and attempts to use subsystem-specific
IDs for virtual device types. These device IDs are also written
in the VG metadata. When no hardware or virtual ID is available,
lvm falls back using the unstable device name as the device ID.
When devnames are used, lvm performs extra scanning to find
devices if their devname changes, e.g. after reboot.
When proper device IDs are used, an lvm command will not look
at devices outside the devices file, but when devnames are used
as a fallback, lvm will scan devices outside the devices file
to locate PVs on renamed devices. A config setting
search_for_devnames can be used to control the scanning for
renamed devname entries.
Related to the devices file, the new command option
--devices <devnames> allows a list of devices to be specified for
the command to use, overriding the devices file. The listed
devices act as a sort of devices file in terms of limiting which
devices lvm will see and use. Devices that are not listed will
appear to be missing to the lvm command.
Multiple devices files can be kept in /etc/lvm/devices, which
allows lvm to be used with different sets of devices, e.g.
system devices do not need to be exposed to a specific application,
and the application can use lvm on its own set of devices that are
not exposed to the system. The option --devicesfile <filename> is
used to select the devices file to use with the command. Without
the option set, the default system devices file is used.
Setting --devicesfile "" causes lvm to not use a devices file.
An existing, empty devices file means lvm will see no devices.
The new command vgimportdevices adds PVs from a VG to the devices
file and updates the VG metadata to include the device IDs.
vgimportdevices -a will import all VGs into the system devices file.
LVM commands run by dmeventd not use a devices file by default,
and will look at all devices on the system. A devices file can
be created for dmeventd (/etc/lvm/devices/dmeventd.devices) If
this file exists, lvm commands run by dmeventd will use it.
Internal implementaion:
- read the devices file
. add struct dev_use (du) struct to cmd->use_devices for each entry
- dev_cache_scan
. add struct device (dev) to dev_cache
- match devices file entries to devices
. match each du on cmd->use_devices to a dev in dev_cache
. sets du->dev, dev->id, dev->flags MATCHED_USE_ID
- label_scan
. filters applied that do not require data from device
. filter-deviceid skips devs without MATCHED_USE_ID, i.e.
devs that are not in the devices file
. read label from dev
. filters applied that require data from device
. read metadata from dev
. lvmcache info/vginfo structs created for PVs/VGs
- handle devices with unstable devname ID where devname changed
. this step only needed when devs do not have proper device IDs,
and their dev names change, e.g. after reboot.
. detect incorrect match because PVID in the devices file entry
does not match the PVID found when the device was read
. undo incorrect device match between du and dev
. search system devices for new location of PVID
. update devices file with new devnames for PVIDs on renamed devices
. label_scan the renamed devs
- continue with command processing
man page updates
|
||
|---|---|---|
| .. | ||
| cmirrord | ||
| dmeventd | ||
| lvmdbusd | ||
| lvmlockd | ||
| lvmpolld | ||
| Makefile.in | ||