2017-03-27 17:45:48 +03:00
.TH "LVM2-ACTIVATION-GENERATOR" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" "\""
2014-03-13 16:01:06 +04:00
.SH "NAME"
2017-03-27 17:45:48 +03:00
lvm2-activation-generator - generator for systemd units to activate LVM2 volumes on boot
2014-03-13 16:01:06 +04:00
.SH SYNOPSIS
2017-03-27 17:45:48 +03:00
.B #SYSTEMD_GENERATOR_DIR#/lvm2-activation-generator
2014-03-13 16:01:06 +04:00
.sp
.SH DESCRIPTION
2017-03-27 17:45:48 +03:00
The lvm2-activation-generator is called by \fBsystemd\fP(1) on boot
2014-03-13 16:01:06 +04:00
to generate systemd units at runtime to activate LVM2 volumes if
\fBlvmetad\fP(8) is disabled (global/use_lvmetad=0 \fBlvm.conf\fP(5)
option is used). Otherwise, if \fBlvmetad\fP(8) is enabled,
2017-03-27 17:45:48 +03:00
the lvm2-activation-generator exits immediately without generating
any systemd units and LVM2 fully relies on event-based activation
2014-03-13 16:01:06 +04:00
to activate the LVM2 volumes instead using the \fBpvscan\fP(8)
2017-03-27 17:45:48 +03:00
(pvscan --cache -aay) call that is a part of \fBudev\fP(8) rules.
2014-03-13 16:01:06 +04:00
2017-03-27 17:45:48 +03:00
These systemd units are generated by lvm2-activation-generator:
2014-03-13 16:01:06 +04:00
.sp
2017-03-27 17:45:48 +03:00
\fIlvm2-activation-early.service\fP
2014-03-13 16:01:06 +04:00
used for activation of LVM2 volumes that is ordered before systemd's
special \fBcryptsetup.target\fP to support LVM2 volumes which are not
layered on top of encrypted devices.
\fIlvm2-activation.service\fP
used for activation of LVM2 volumes that is ordered after systemd's
special \fBcryptsetup.target\fP to support LVM2 volumes which are
layered on top of encrypted devices.
2017-03-27 17:45:48 +03:00
\fIlvm2-activation-net.service\fP
2014-03-13 16:01:06 +04:00
used for activation of LVM2 volumes that is ordered after systemd's
2017-03-27 17:45:48 +03:00
special \fBremote-fs-pre.target\fP to support LVM2 volumes which are
2015-09-23 14:17:12 +03:00
layered on attached remote devices.
2014-03-13 16:01:06 +04:00
Note that all the underlying devices (Physical Volumes) need to be present
when the service is run. If the there are any devices presented in the system
anytime later, any LVM2 volumes on top of such devices need to be activated
directly by \fBlvchange\fP(8) or \fBvgchange\fP(8). This limitation does
2017-03-27 17:45:48 +03:00
not exist when using \fBlvmetad\fP(8) and accompanying event-based activation
2014-03-13 16:01:06 +04:00
since such LVM volumes are activated automatically as soon as the Volume Group
is ready (all the Physical Volumes making up the Volume Group are present
in the system).
2017-03-27 17:45:48 +03:00
The lvm2-activation-generator implements the \fBGenerators Specification\fP
2014-03-13 16:01:06 +04:00
as referenced in \fBsystemd\fP(1).
.sp
.SH SEE ALSO
.BR lvm.conf (5)
.BR vgchange (8)
.BR lvchange (8)
.BR lvmetad (8)
.BR pvscan (8)
.BR udev (7)
.BR systemd (1)
.BR systemd.target (5)
.BR systemd.special (7)