shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity

man pvscan: just write --activate in description

Browse Source 
rather than -a|--activate, because web pages on
man7.org are not printing the | character.
This commit is contained in:
David Teigland 2017-09-18 10:56:39 -05:00
parent d73eddcdc0
commit 200793edc6
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
man/pvscan.8_des
View File

@ -64,8 +64,7 @@ When event-driven system services detect a new LVM device, the first step
is to automatically scan and cache the metadata from the device. This is
done by pvscan --cache. A second step is to automatically activate LVs
that are present on the new device. This auto-activation is done by the
same pvscan --cache command when the option '-a|--activate ay' is
included.
same pvscan --cache command when the option --activate ay is included.
Auto-activation of VGs or LVs can be enabled/disabled using:
.br
@ -80,11 +79,11 @@ When this setting is undefined, all LVs are auto-activated (when lvm is
fully integrated with the event-driven system services.)
When a VG or LV is not auto-activated, traditional activation using
vgchange or lvchange -a|--activate is needed.
vgchange or lvchange --activate is needed.
.IP \[bu] 2
pvscan auto-activation can be only done in combination with --cache.
.IP \[bu] 2
Auto-activation is designated by the "a" argument in '-a|--activate ay'.
Auto-activation is designated by the "a" argument in --activate ay.
This is meant to distinguish system generated commands from explicit user
commands, although it can be used in any activation command. Whenever it
is used, the auto_activation_volume_list is applied.