2008-10-08 16:50:13 +04:00
.TH LVCHANGE 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
2002-01-04 23:35:19 +03:00
.SH NAME
lvchange \- change attributes of a logical volume
.SH SYNOPSIS
.B lvchange
2012-04-11 16:42:10 +04:00
.RB [ \- \- addtag
.IR Tag ]
.RB [ \- A | \- \- autobackup
.RI { y | n }]
2012-06-27 15:48:31 +04:00
.RB [ \- a | \- \- activate
2012-06-29 14:40:26 +04:00
.RI [ a | e | l ]{ y | n }]
2013-07-11 14:44:36 +04:00
.RB [ \- k | \- \- setactivationskip { y | n } ]
.RB [ \- K | \- \- ignoreactivationskip ]
2012-04-11 16:42:10 +04:00
.RB [ \- \- alloc
.IR AllocationPolicy ]
.RB [ \- C | \- \- contiguous
.RI { y | n }]
.RB [ \- d | \- \- debug ]
.RB [ \- \- deltag
.IR Tag ]
2013-07-03 18:45:27 +04:00
.RB [ \- \- profile
.IR ProfileName ]
.RB [ \- \- detachprofile ]
2012-08-08 00:24:41 +04:00
.RB [ \- \- discards
2012-06-28 16:52:23 +04:00
.RI { ignore | nopassdown | passdown }]
2012-04-11 16:42:10 +04:00
.RB [ \- \- resync ]
.RB [ \- h | \- ? | \- \- help ]
.RB [ \- \- ignorelockingfailure ]
.RB [ \- \- ignoremonitoring ]
.RB [ \- \- monitor
.RI { y | n }]
.RB [ \- \- poll
.RI { y | n }]
2013-05-31 20:25:52 +04:00
.RB [ \- \- maxrecoveryrate
.IR Rate ]
.RB [ \- \- minrecoveryrate
.IR Rate ]
2013-04-12 00:33:59 +04:00
.RB [ \- \- syncaction
.RI { check | repair }]
2012-04-11 16:42:10 +04:00
.RB [ \- \- sysinit ]
.RB [ \- \- noudevsync ]
.RB [ \- M | \- \- persistent
.RI { y | n }]
.RB [ \- \- minor
.IR minor ]
.RB [ \- P | \- \- partial ]
.RB [ \- p | \- \- permission
.RI { r | rw }]
.RB [ \- r | \- \- readahead
.RI { ReadAheadSectors | auto | none }]
.RB [ \- \- refresh ]
.RB [ \- t | \- \- test ]
2012-06-28 16:52:23 +04:00
.RB [ \- v | \- \- verbose ]
RAID: Add writemostly/writebehind support for RAID1
'lvchange' is used to alter a RAID 1 logical volume's write-mostly and
write-behind characteristics. The '--writemostly' parameter takes a
PV as an argument with an optional trailing character to specify whether
to set ('y'), unset ('n'), or toggle ('t') the value. If no trailing
character is given, it will set the flag.
Synopsis:
lvchange [--writemostly <PV>:{t|y|n}] [--writebehind <count>] vg/lv
Example:
lvchange --writemostly /dev/sdb1:y --writebehind 512 vg/raid1_lv
The last character in the 'lv_attr' field is used to show whether a device
has the WriteMostly flag set. It is signified with a 'w'. If the device
has failed, the 'p'artial flag has priority.
Example ("nosync" raid1 with mismatch_cnt and writemostly):
[~]# lvs -a --segment vg
LV VG Attr #Str Type SSize
raid1 vg Rwi---r-m 2 raid1 500.00m
[raid1_rimage_0] vg Iwi---r-- 1 linear 500.00m
[raid1_rimage_1] vg Iwi---r-w 1 linear 500.00m
[raid1_rmeta_0] vg ewi---r-- 1 linear 4.00m
[raid1_rmeta_1] vg ewi---r-- 1 linear 4.00m
Example (raid1 with mismatch_cnt, writemostly - but failed drive):
[~]# lvs -a --segment vg
LV VG Attr #Str Type SSize
raid1 vg rwi---r-p 2 raid1 500.00m
[raid1_rimage_0] vg Iwi---r-- 1 linear 500.00m
[raid1_rimage_1] vg Iwi---r-p 1 linear 500.00m
[raid1_rmeta_0] vg ewi---r-- 1 linear 4.00m
[raid1_rmeta_1] vg ewi---r-p 1 linear 4.00m
A new reportable field has been added for writebehind as well. If
write-behind has not been set or the LV is not RAID1, the field will
be blank.
Example (writebehind is set):
[~]# lvs -a -o name,attr,writebehind vg
LV Attr WBehind
lv rwi-a-r-- 512
[lv_rimage_0] iwi-aor-w
[lv_rimage_1] iwi-aor--
[lv_rmeta_0] ewi-aor--
[lv_rmeta_1] ewi-aor--
Example (writebehind is not set):
[~]# lvs -a -o name,attr,writebehind vg
LV Attr WBehind
lv rwi-a-r--
[lv_rimage_0] iwi-aor-w
[lv_rimage_1] iwi-aor--
[lv_rmeta_0] ewi-aor--
[lv_rmeta_1] ewi-aor--
2013-04-15 22:59:46 +04:00
.RB [ \- \- writebehind BehindCount ]
.RB [ \- \- writemostly PhysicalVolume ]
2012-06-28 16:52:23 +04:00
.RB [ \- Z | \- \- zero
.RI { y | n }]
2012-04-11 16:42:10 +04:00
.I LogicalVolumePath
.RI [ LogicalVolumePath ...]
2002-01-04 23:35:19 +03:00
.SH DESCRIPTION
2004-11-12 18:59:09 +03:00
lvchange allows you to change the attributes of a logical volume
including making them known to the kernel ready for use.
2002-01-04 23:35:19 +03:00
.SH OPTIONS
2012-04-11 16:42:10 +04:00
See \fB lvm\fP (8) for common options.
2002-01-04 23:35:19 +03:00
.TP
2012-06-29 14:40:26 +04:00
.BR \- a ", " \- \- activate " [" \fI a | \fI e | \fI l ]{ \fI y | \fI n }
2002-01-04 23:35:19 +03:00
Controls the availability of the logical volumes for use.
2004-11-12 18:59:09 +03:00
Communicates with the kernel device-mapper driver via
2012-04-11 16:42:10 +04:00
libdevmapper to activate (\- ay) or deactivate (\- an) the
2012-06-29 14:40:26 +04:00
logical volumes. If autoactivation option is used (\- aay),
the logical volume is activated only if it matches an item in
the activation/auto_activation_volume_list set in lvm.conf.
2013-06-14 11:36:56 +04:00
If this list is not set, then all volumes are considered for
autoactivation. The autoactivation is not yet supported for
logical volumes that are part of partial or clustered volume groups.
2004-11-12 18:59:09 +03:00
.IP
2008-06-02 19:54:32 +04:00
If clustered locking is enabled, -aey will activate exclusively
2004-11-12 18:59:09 +03:00
on one node and -aly will activate only on the local node.
To deactivate only on the local node use -aln.
2012-04-11 16:42:10 +04:00
Logical volumes with single-host snapshots are always activated
2004-11-12 18:59:09 +03:00
exclusively because they can only be used on one node at once.
2002-01-04 23:35:19 +03:00
.TP
2013-07-11 14:44:36 +04:00
.BR \- k ", " \- \- setactivationskip " {" \fI y | \fI n }
Controls whether Logical Volumes are persistently flagged to be
skipped during activation. By default, thin snapshot volumes are
flagged for activation skip. To activate such volumes,
an extra \fB \- K/\- \- ignoreactivationskip\fP option must be used.
The flag is not applied during deactivation. To see whether
the flag is attached, use \fB lvs\fP command where the state
of the flag is reported within \fB lv_attr\fP bits.
.TP
.BR \- K ", " \- \- ignoreactivationskip
Ignore the flag to skip Logical Volumes during activation.
.TP
2012-04-11 16:42:10 +04:00
.BR \- C ", " \- \- contiguous " {" \fI y | \fI n }
2002-11-18 17:04:08 +03:00
Tries to set or reset the contiguous allocation policy for
2002-01-04 23:35:19 +03:00
logical volumes. It's only possible to change a non-contiguous
logical volume's allocation policy to contiguous, if all of the
allocated physical extents are already contiguous.
.TP
2013-07-03 18:45:27 +04:00
.BR \- \- detachprofile
Detach any configuration profiles attached to given Logical Volumes.
See also \fB lvm\fP (8) and \fB lvm.conf\fP (5) for more
information about configuration profiles.
.TP
2012-08-08 00:24:41 +04:00
.BR \- \- discards " {" \fI ignore | \fI nopassdown | \fI passdown }
2012-08-07 23:20:16 +04:00
Set this to \fI ignore\fP to ignore any discards received by a
thin pool Logical Volume. Set to \fI nopassdown\fP to process such
discards within the thin pool itself and allow the no-longer-needed
2012-08-08 00:24:41 +04:00
extents to be overwritten by new data. Set to \fI passdown\fP (the
default) to process them both within the thin pool itself and to
pass them down the underlying device.
2012-06-28 16:52:23 +04:00
.TP
2012-04-11 16:42:10 +04:00
.B \- \- resync
2006-10-24 21:09:40 +04:00
Forces the complete resynchronization of a mirror. In normal
circumstances you should not need this option because synchronization
happens automatically. Data is read from the primary mirror device
and copied to the others, so this can take a considerable amount of
time - and during this time you are without a complete redundant copy
of your data.
2006-10-24 03:03:55 +04:00
.TP
2012-04-11 16:42:10 +04:00
.B \- \- minor \fI minor
2002-11-18 17:04:08 +03:00
Set the minor number.
.TP
2012-04-11 16:42:10 +04:00
.BR \- \- monitor " {" \fI y | \fI n }
2010-03-24 01:30:18 +03:00
Start or stop monitoring a mirrored or snapshot logical volume with
2006-08-19 02:27:01 +04:00
dmeventd, if it is installed.
If a device used by a monitored mirror reports an I/O error,
2012-04-11 16:42:10 +04:00
the failure is handled according to
2006-08-19 02:27:01 +04:00
\fB mirror_image_fault_policy\fP and \fB mirror_log_fault_policy\fP
set in \fB lvm.conf\fP .
2006-08-19 01:49:19 +04:00
.TP
2012-04-11 16:42:10 +04:00
.BR \- \- poll " {" \fI y | \fI n }
2010-01-06 22:08:58 +03:00
Without polling a logical volume's backgrounded transformation process
will never complete. If there is an incomplete pvmove or lvconvert (for
2012-04-11 16:42:10 +04:00
example, on rebooting after a crash), use \fB \- \- poll y\fP to restart the
2010-01-06 22:08:58 +03:00
process from its last checkpoint. However, it may not be appropriate to
2012-04-11 16:42:10 +04:00
immediately poll a logical volume when it is activated, use
\fB \- \- poll n\fP to defer and then \fB \- \- poll y\fP to restart the process.
2010-01-05 23:56:51 +03:00
.TP
2013-05-31 20:25:52 +04:00
.IR \fB \- \- maxrecoveryrate " " \fI Rate [ bBsSkKmMgG ]
Sets the maximum recovery rate for a RAID logical volume. \fI Rate\fP
is specified as a size/sec/device. If no suffix is given, then
kiB/sec/device is assumed. Setting the recovery rate to 0 means
it will be unbounded.
.TP
.IR \fB \- \- minrecoveryrate " " \fI Rate [ bBsSkKmMgG ]
Sets the minimum recovery rate for a RAID logical volume. \fI Rate\fP
is specified as a size/sec/device. If no suffix is given, then
kiB/sec/device is assumed. Setting the recovery rate to 0 means
it will be unbounded.
.TP
2013-04-12 00:33:59 +04:00
.BR \- \- syncaction " {" \fI check | \fI repair }
This argument is used to initiate various RAID synchronization operations.
The \fI check\fP and \fI repair\fP options provide a way to check the
integrity of a RAID logical volume (often referred to as "scrubbing").
These options cause the RAID logical volume to
read all of the data and parity blocks in the array and check for any
discrepancies (e.g. mismatches between mirrors or incorrect parity values).
If \fI check\fP is used, the discrepancies will be counted but not repaired.
If \fI repair\fP is used, the discrepancies will be corrected as they are
encountered. The 'lvs' command can be used to show the number of
discrepancies found or repaired.
.TP
2012-04-11 16:42:10 +04:00
.B \- \- sysinit
Indicates that \fB lvchange\fP (8) is being invoked from early system
initialisation scripts (e.g. rc.sysinit or an initrd),
before writeable filesystems are available. As such,
some functionality needs to be disabled and this option
2010-05-06 15:15:55 +04:00
acts as a shortcut which selects an appropriate set of options. Currently
2012-04-11 16:42:10 +04:00
this is equivalent to using \fB \- \- ignorelockingfailure\fP ,
\fB \- \- ignoremonitoring\fP , \fB \- \- poll n\fP and setting
\fB LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES\fP
2010-05-06 15:15:55 +04:00
environment variable.
2012-07-10 15:49:46 +04:00
If \fB \- \- sysinit\fP is used in conjunction with lvmetad(8) enabled and running,
autoactivation is preferred over manual activation via direct lvchange call.
Logical volumes are autoactivated according to auto_activation_volume_list
set in lvm.conf(5).
2010-05-06 15:15:55 +04:00
.TP
2012-04-11 16:42:10 +04:00
.B \- \- noudevsync
2009-08-03 14:58:40 +04:00
Disable udev synchronisation. The
process will not wait for notification from udev.
It will continue irrespective of any possible udev processing
in the background. You should only use this if udev is not running
or has rules that ignore the devices LVM2 creates.
.TP
2012-04-11 16:42:10 +04:00
.B \- \- ignoremonitoring
Make no attempt to interact with dmeventd unless \fB \- \- monitor\fP
2007-06-18 18:14:33 +04:00
is specified.
Do not use this if dmeventd is already monitoring a device.
.TP
2012-04-11 16:42:10 +04:00
.BR \- M ", " \- \- persistent " {" \fI y | \fI n }
2002-11-18 17:04:08 +03:00
Set to y to make the minor number specified persistent.
.TP
2012-04-11 16:42:10 +04:00
.BR \- p ", " \- \- permission " {" \fI r | \fI rw }
2002-01-04 23:35:19 +03:00
Change access permission to read-only or read/write.
.TP
2012-04-11 16:42:10 +04:00
.BR \- r ", " \- \- readahead " {" \fI ReadAheadSectors | \fI auto | \fI none }
2007-11-09 19:51:54 +03:00
Set read ahead sector count of this logical volume.
For volume groups with metadata in lvm1 format, this must
2007-12-06 01:11:20 +03:00
be a value between 2 and 120 sectors.
2007-11-09 19:51:54 +03:00
The default value is "auto" which allows the kernel to choose
a suitable value automatically.
"None" is equivalent to specifying zero.
2004-11-12 18:59:09 +03:00
.TP
2012-04-11 16:42:10 +04:00
.B \- \- refresh
2004-11-12 18:59:09 +03:00
If the logical volume is active, reload its metadata.
This is not necessary in normal operation, but may be useful
2012-04-11 16:42:10 +04:00
if something has gone wrong or if you're doing clustering
2004-11-12 18:59:09 +03:00
manually without a clustered lock manager.
2012-06-28 16:52:23 +04:00
.TP
RAID: Add writemostly/writebehind support for RAID1
'lvchange' is used to alter a RAID 1 logical volume's write-mostly and
write-behind characteristics. The '--writemostly' parameter takes a
PV as an argument with an optional trailing character to specify whether
to set ('y'), unset ('n'), or toggle ('t') the value. If no trailing
character is given, it will set the flag.
Synopsis:
lvchange [--writemostly <PV>:{t|y|n}] [--writebehind <count>] vg/lv
Example:
lvchange --writemostly /dev/sdb1:y --writebehind 512 vg/raid1_lv
The last character in the 'lv_attr' field is used to show whether a device
has the WriteMostly flag set. It is signified with a 'w'. If the device
has failed, the 'p'artial flag has priority.
Example ("nosync" raid1 with mismatch_cnt and writemostly):
[~]# lvs -a --segment vg
LV VG Attr #Str Type SSize
raid1 vg Rwi---r-m 2 raid1 500.00m
[raid1_rimage_0] vg Iwi---r-- 1 linear 500.00m
[raid1_rimage_1] vg Iwi---r-w 1 linear 500.00m
[raid1_rmeta_0] vg ewi---r-- 1 linear 4.00m
[raid1_rmeta_1] vg ewi---r-- 1 linear 4.00m
Example (raid1 with mismatch_cnt, writemostly - but failed drive):
[~]# lvs -a --segment vg
LV VG Attr #Str Type SSize
raid1 vg rwi---r-p 2 raid1 500.00m
[raid1_rimage_0] vg Iwi---r-- 1 linear 500.00m
[raid1_rimage_1] vg Iwi---r-p 1 linear 500.00m
[raid1_rmeta_0] vg ewi---r-- 1 linear 4.00m
[raid1_rmeta_1] vg ewi---r-p 1 linear 4.00m
A new reportable field has been added for writebehind as well. If
write-behind has not been set or the LV is not RAID1, the field will
be blank.
Example (writebehind is set):
[~]# lvs -a -o name,attr,writebehind vg
LV Attr WBehind
lv rwi-a-r-- 512
[lv_rimage_0] iwi-aor-w
[lv_rimage_1] iwi-aor--
[lv_rmeta_0] ewi-aor--
[lv_rmeta_1] ewi-aor--
Example (writebehind is not set):
[~]# lvs -a -o name,attr,writebehind vg
LV Attr WBehind
lv rwi-a-r--
[lv_rimage_0] iwi-aor-w
[lv_rimage_1] iwi-aor--
[lv_rmeta_0] ewi-aor--
[lv_rmeta_1] ewi-aor--
2013-04-15 22:59:46 +04:00
.BR \- \- writebehind " BehindCount"
Specify the maximum number of outstanding writes that are allowed to
devices in a RAID 1 logical volume that are marked as \fI write-mostly\fP .
Once this value is exceeded, writes become synchronous (i.e. all writes
to the constituent devices must complete before the array signals the
write has completed). Setting the value to zero clears the preference
and allows the system to choose the value arbitrarily.
.TP
.BR \- \- writemostly " PhysicalVolume[:{t|y|n}]"
Mark a device in a RAID1 logical volume as \fI write-mostly\fP . All reads
to these drives will be avoided unless absolutely necessary. This keeps
the number of I/Os to the drive to a minimum. The default behavior is to
set the write-mostly attribute for the specified physical volume in the
logical volume. It is possible to also remove the write-mostly flag by
appending a ":n" to the physical volume or to toggle the value by specifying
":t". The \fI --writemostly\fP argument can be specified more than one time
in a single command; making it possible to toggle the write-mostly attributes
for all the physical volumes in a logical volume at once.
.TP
2012-06-28 16:52:23 +04:00
.BR \- Z ", " \- \- zero " {" \fI y | \fI n }
Set zeroing mode for thin pool. Note: already provisioned blocks from pool
in non-zero mode are not cleared in unwritten parts when setting zero to
\fI y\fP .
2002-01-04 23:35:19 +03:00
.SH Examples
2012-04-11 16:42:10 +04:00
Changes the permission on volume lvol1 in volume group vg00 to be read-only:
.sp
.B lvchange -pr vg00/lvol1
2002-01-04 23:35:19 +03:00
.SH SEE ALSO
2012-04-11 16:42:10 +04:00
.BR lvm (8),
2004-11-12 18:59:09 +03:00
.BR lvcreate (8),
.BR vgchange (8)