1
0
mirror of git://sourceware.org/git/lvm2.git synced 2025-01-04 09:18:36 +03:00

man vgchange lvchange: mention activation option s

and improve the existing text about existing
activation options.
This commit is contained in:
David Teigland 2015-06-16 13:28:07 -05:00
parent 857296c823
commit 3d9957e3dd
2 changed files with 68 additions and 18 deletions

View File

@ -8,7 +8,7 @@ lvchange \(em change attributes of a logical volume
.RB [ \-A | \-\-autobackup .RB [ \-A | \-\-autobackup
.RI { y | n }] .RI { y | n }]
.RB [ \-a | \-\-activate .RB [ \-a | \-\-activate
.RI [ a | e | l ]{ y | n }] .RI [ a | e | s | l ]{ y | n }]
.RB [ \-\-activationmode .RB [ \-\-activationmode
.RI { complete | degraded | partial }] .RI { complete | degraded | partial }]
.RB [ \-k | \-\-setactivationskip .RB [ \-k | \-\-setactivationskip
@ -81,7 +81,7 @@ including making them known to the kernel ready for use.
.SH OPTIONS .SH OPTIONS
See \fBlvm\fP(8) for common options. See \fBlvm\fP(8) for common options.
.TP .TP
.BR \-a ", " \-\-activate " [" \fIa | \fIe | \fIl ]{ \fIy | \fIn } .BR \-a ", " \-\-activate " [" \fIa | \fIe | \fIs | \fIl ]{ \fIy | \fIn }
Controls the availability of the logical volumes for use. Controls the availability of the logical volumes for use.
Communicates with the kernel device-mapper driver via Communicates with the kernel device-mapper driver via
libdevmapper to activate (\-ay) or deactivate (\-an) the libdevmapper to activate (\-ay) or deactivate (\-an) the
@ -104,11 +104,36 @@ activation. The \-aay option should be also used during system
boot so it's possible to select which volumes to activate using boot so it's possible to select which volumes to activate using
the activation/auto_activation_volume_list setting. the activation/auto_activation_volume_list setting.
.IP .IP
If clustered locking is enabled, -aey will activate exclusively In a clustered VG, clvmd is used for activation, and the
on one node and -aly will activate only on the local node. following options are possible:
To deactivate only on the local node use -aln.
Logical volumes with single-host snapshots are always activated With \-aey, clvmd activates the LV in exclusive mode
exclusively because they can only be used on one node at once. (with an exclusive lock), allowing a single node to activate the LV.
With \-asy, clvmd activates the LV in shared mode
(with a shared lock), allowing multiple nodes to activate the LV concurrently.
If the LV type prohibits shared access, such as an LV with a snapshot,
the 's' option is ignored and an exclusive lock is used.
With \-ay (no mode specified), clvmd activates the LV in shared mode
if the LV type allows concurrent access, such as a linear LV.
Otherwise, clvmd activates the LV in exclusive mode.
With \-aey, \-asy, and \-ay, clvmd attempts to activate the LV
on all nodes. If exclusive mode is used, then only one of the
nodes will be successful.
With \-an, clvmd attempts to deactivate the LV on all nodes.
With \-aly, clvmd activates the LV only on the local node, and \-aln
deactivates only on the local node. If the LV type allows concurrent
access, then shared mode is used, otherwise exclusive.
LVs with snapshots are always activated exclusively because they can only
be used on one node at once.
For local VGs, \-ay, \-aey, and \-asy are all equivalent.
.TP .TP
.BR \-\-activationmode " {" \fIcomplete | \fIdegraded | \fIpartial } .BR \-\-activationmode " {" \fIcomplete | \fIdegraded | \fIpartial }
The activation mode determines whether logical volumes are allowed to The activation mode determines whether logical volumes are allowed to

View File

@ -10,7 +10,7 @@ vgchange \(em change attributes of a volume group
.RB [ \-A | \-\-autobackup .RB [ \-A | \-\-autobackup
.RI { y | n }] .RI { y | n }]
.RB [ \-a | \-\-activate .RB [ \-a | \-\-activate
.RI [ a | e | l ] .RI [ a | e | s | l ]
.RI { y | n }] .RI { y | n }]
.RB [ \-\-activationmode .RB [ \-\-activationmode
.IR { complete | degraded | partial } ] .IR { complete | degraded | partial } ]
@ -77,7 +77,7 @@ Controls automatic backup of metadata after the change. See
.BR vgcfgbackup (8). .BR vgcfgbackup (8).
Default is yes. Default is yes.
.TP .TP
.BR \-a ", " \-\-activate " [" \fIa | \fIe | \fIl ]{ \fIy | \fIn } .BR \-a ", " \-\-activate " [" \fIa | \fIe | \fIs | \fIl ]{ \fIy | \fIn }
Controls the availability of the logical volumes in the volume Controls the availability of the logical volumes in the volume
group for input/output. group for input/output.
In other words, makes the logical volumes known/unknown to the kernel. In other words, makes the logical volumes known/unknown to the kernel.
@ -98,24 +98,49 @@ The location and name of the underlying device node may depend on
the distribution and configuration (e.g. udev) and might change the distribution and configuration (e.g. udev) and might change
from release to release. from release to release.
.IP .IP
If clustered locking is enabled, add 'e' to activate/deactivate In a clustered VG, clvmd is used for activation, and the
exclusively on one node or 'l' to activate/deactivate only following options are possible:
on the local node.
Logical volumes with single-host snapshots are always activated With \-aey, clvmd activates the LV in exclusive mode
exclusively because they can only be used on one node at once. (with an exclusive lock), allowing a single node to activate the LV.
With \-asy, clvmd activates the LV in shared mode
(with a shared lock), allowing multiple nodes to activate the LV concurrently.
If the LV type prohibits shared access, such as an LV with a snapshot,
the 's' option is ignored and an exclusive lock is used.
With \-ay (no mode specified), clvmd activates the LV in shared mode
if the LV type allows concurrent access, such as a linear LV.
Otherwise, clvmd activates the LV in exclusive mode.
With \-aey, \-asy, and \-ay, clvmd attempts to activate the LV
on all nodes. If exclusive mode is used, then only one of the
nodes will be successful.
With \-an, clvmd attempts to deactivate the LV on all nodes.
With \-aly, clvmd activates the LV only on the local node, and \-aln
deactivates only on the local node. If the LV type allows concurrent
access, then shared mode is used, otherwise exclusive.
LVs with snapshots are always activated exclusively because they can only
be used on one node at once.
For local VGs, \-ay, \-aey, and \-asy are all equivalent.
.TP .TP
.BR \-\-activationmode " {" \fIcomplete | \fIdegraded | \fIpartial } .BR \-\-activationmode " {" \fIcomplete | \fIdegraded | \fIpartial }
The activation mode determines whether logical volumes are allowed to The activation mode determines whether logical volumes are allowed to
activate when there are physical volumes missing (e.g. due to a device activate when there are physical volumes missing (e.g. due to a device
failure). \fIcomplete is the most restrictive; allowing only those failure). \fIcomplete\fP is the most restrictive; allowing only those
logical volumes to be activated that are not affected by the missing logical volumes to be activated that are not affected by the missing
PVs. \fIdegraded allows RAID logical volumes to be activated even if PVs. \fIdegraded\fP allows RAID logical volumes to be activated even if
they have PVs missing. (Note that the "mirror" segment type is not they have PVs missing. (Note that the "mirror" segment type is not
considered a RAID logical volume. The "raid1" segment type should considered a RAID logical volume. The "raid1" segment type should
be used instead.) Finally, \fIpartial allows any logical volume to be used instead.) Finally, \fIpartial\fP allows any logical volume to
be activated even if portions are missing due to a missing or failed be activated even if portions are missing due to a missing or failed
PV. This last option should only be used when performing recovery or PV. This last option should only be used when performing recovery or
repair operations. \fIdegraded is the default mode. To change it, modify repair operations. \fIdegraded\fP is the default mode. To change it, modify
.B activation_mode .B activation_mode
in in
.BR lvm.conf (5). .BR lvm.conf (5).