mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-22 17:35:59 +03:00
353718785f
With to use .TP where it's easy and doesn't change layout (since .HP is marked as deprecated) - but .TP is not always perfetc match. Avoid submitting empty lines to troff and replace them mostly with .P and use '.' at line start to preserve 'visual' presence of empty line while editing man page manually when there is no extra space needed. Fix some markup. Add some missing SEE ALSO section. Drop some white-space at end-of-lines. Improve hyphenation logic so we do not split options. Use '.IP numbers' only with first one the row (others in row automatically derive this value) Use automatic enumeration for .SH titles. Guidelines in-use: https://man7.org/linux/man-pages/man7/groff.7.html https://www.gnu.org/software/groff/manual/html_node/Man-usage.html https://www.gnu.org/software/groff/manual/html_node/Lists-in-ms.html
59 lines
1.8 KiB
Plaintext
59 lines
1.8 KiB
Plaintext
.TH "LVM2-ACTIVATION-GENERATOR" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" "\""
|
|
.
|
|
.SH "NAME"
|
|
.
|
|
lvm2-activation-generator - generator for systemd units to activate LVM volumes on boot
|
|
.
|
|
.SH SYNOPSIS
|
|
.
|
|
.B #SYSTEMD_GENERATOR_DIR#/lvm2-activation-generator
|
|
.
|
|
.SH DESCRIPTION
|
|
.
|
|
The lvm2-activation-generator is called by \fBsystemd\fP(1) on boot to
|
|
generate systemd units at runtime to activate LVM Logical Volumes (LVs)
|
|
when global/event_activation=0 is set in \fBlvm.conf\fP(5). These units use
|
|
\fBvgchange -aay\fP to activate LVs.
|
|
.P
|
|
If event_activation=1, the lvm2-activation-generator exits immediately without
|
|
generating any systemd units, and LVM fully relies on event-based
|
|
activation to activate LVs. In this case, event-generated
|
|
.B pvscan --cache -aay
|
|
commands activate LVs.
|
|
.P
|
|
These systemd units are generated by lvm2-activation-generator:
|
|
.P
|
|
.I lvm2-activation-early.service
|
|
is run before systemd's special \fBcryptsetup.target\fP to activate
|
|
LVs that are not layered on top of encrypted devices.
|
|
.P
|
|
.I lvm2-activation.service
|
|
is run after systemd's special \fBcryptsetup.target\fP to activate
|
|
LVs that are layered on top of encrypted devices.
|
|
.P
|
|
.I lvm2-activation-net.service
|
|
is run after systemd's special \fBremote-fs-pre.target\fP to activate
|
|
LVs that are layered on attached remote devices.
|
|
.P
|
|
Note that all the underlying LVM devices (Physical Volumes) need to be
|
|
present when the service is run. If the there are any devices that appear
|
|
to the system later, LVs using these devices need to be activated directly
|
|
by \fBlvchange\fP(8) or \fBvgchange\fP(8).
|
|
.P
|
|
The lvm2-activation-generator implements the \fBGenerators Specification\fP
|
|
as referenced in \fBsystemd\fP(1).
|
|
.
|
|
.SH SEE ALSO
|
|
.nh
|
|
.ad l
|
|
.BR lvm.conf (5),
|
|
.BR vgchange (8),
|
|
.BR lvchange (8),
|
|
.BR pvscan (8),
|
|
.P
|
|
.BR systemd (1),
|
|
.BR systemd.target (5),
|
|
.BR systemd.special (7),
|
|
.P
|
|
.BR udev (7)
|