Introduction to LVM2
The LVM2 package is a set of tools
that manage logical partitions. It allows spanning of file systems
across multiple physical disks and disk partitions and provides for
dynamic growing or shrinking of logical partitions, mirroring and
low storage footprint snapshots.
This package is known to build and work properly using an LFS-7.9
This package is known to build properly using the gcc-6 compiler.
Download MD5 sum: 8e8025f2d82861c7285e2a36c58d279c
Download size: 1.9 MB
Estimated disk space required: 27 MB (add 19 MB for tests,
however transient files can grow up to around 500 MB)
Estimated build time: 0.4 SBU (add 6.0 SBU for tests)
reiserfsprogs-3.6.25, Valgrind-3.11.0, Which-2.21, xfsprogs-4.5.0 (all five
may be used, but are not required, for tests), and thin-provisioning-tools
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/lvm2
Kernel versions between 4.1 and 4.4.1 have a broken RAID
implementation. If you want to use RAID type LV's, you should
install kernel version 4.4.2 or above. Note that several tests
use RAID logical volumes, and can generate a “kernel oops” with the faulty kernel version,
which usually renders the system unusable.
Enable the following options in the kernel configuration and
recompile the kernel:
There are several other Device Mapper options in the kernel
beyond those listed below. In order to get reasonable results if
running the regression tests, all must be enabled either
internally or as a module. The tests will all time out if Magic
SysRq key is not enabled.
Device Drivers --->
[*] Multiple devices driver support (RAID and LVM) ---> [CONFIG_MD]
<*/M> Device mapper support [CONFIG_BLK_DEV_DM]
<*/M/ > Crypt target support [CONFIG_DM_CRYPT]
<*/M/ > Snapshot target [CONFIG_DM_SNAPSHOT]
<*/M/ > Thin provisioning target [CONFIG_DM_THIN_PROVISIONING]
<*/M/ > Mirror target [CONFIG_DM_MIRROR]
Kernel hacking --->
[*] Magic SysRq key [CONFIG_MAGIC_SYSRQ]
Installation of LVM2
Install LVM2 by running the
./configure --prefix=/usr \
The tests use udev for logical
volume synchronization, so that the LVM udev rules and some
utilities need to be installed before running the tests. If you are
installing LVM2 for the first
time, and do not want to install the full package before running
the tests, the minimal set of utilities can be installed by running
the following instructions as the
make -C tools install_dmsetup_dynamic &&
make -C udev install &&
make -C libdm install
To test the results, issue: make
check_local as the
root user. Other targets are available and can
be listed with make -C test
help. The test timings are very dependent on the
speed of the disk(s), and on the number of enabled kernel options.
Those tests do not implement the “expected fail” possibility, and a small number
of test failures is expected by upstream. More failures may happen
because some kernel options are missing. For example, the lack of
the dm-delay device mapper
target may explain somefailures. Some tests are flagged
“warned” if thin-provisioning-tools
are not installed. A workaround is to add the following flags to
Some tests may hang with kernel versions in the 4.1 and 4.2 series
(see above). They can be removed if necessary, for example:
test/shell/lvcreate-large-raid.sh. The tests
generate a lot of kernel messages, which may clutter your terminal.
You can disable them by issuing dmesg
-D before running the tests (do not forget to issue
dmesg -E when tests
Now, as the
path must contain
/usr/sbin for proper system tool
detection by the configure script. This
instruction ensures that PATH is properly set even if you build as
an unprivileged user.
switch enables building of the shared application library.
switch enables building of the shared command library. It is
required when building the event daemon.
switch enables installation of pkg-config support files.
switch enables synchronisation with Udev processing.
--enable-dmeventd: This switch enables
building of the Device Mapper
--enable-lvmetad: This switch enables
building of the LVM metadata
daemon, which avoids scanning all the filesystems when an lvm
command is run.
blkdeactivate, dmeventd (optional),
dmsetup, fsadm, lvm, lvmconf, lvmdump, lvmetad (optional), and
vgimportclone. There are also numerous symbolic links to lvm
that implement specific functionalities
libdevmapper.so, liblvm2app.so, and
liblvm2cmd.so; optional: libdevmapper-event.so,
/etc/lvm and /lib/device-mapper
is a utility to deactivate block device.
(optional) is the Device Mapper event daemon.
is a low level logical volume management tool.
is a utility used to resize or check filesystem on a
provides the command-line tools for LVM2. Commands are implemented via
sympolic links to this program to manage physical devices
(pv*), volume groups (vg*) and logical volumes (lv*).
is a script that modifies the locking configuration in
the LVM2 configuration
is a tool used to dump various information concerning
(optional) is the LVM metadata daemon.
is used to import a duplicated VG (e.g. hardware
contains the Device
Mapper API functions.
Last updated on 2016-06-10 13:43:02 -0500