diff options
author | Zdenek Kabelac <zkabelac@redhat.com> | 2012-01-20 10:50:39 +0000 |
---|---|---|
committer | Zdenek Kabelac <zkabelac@redhat.com> | 2012-01-20 10:50:39 +0000 |
commit | 43254b118569c12bdf614f7822907b49aa0713b6 (patch) | |
tree | 652d8408f57e983391e609179b3bb2a1fe2f0608 | |
parent | b2b316ab51269f70a8a7d161b78c198b2a8eae02 (diff) | |
download | lvm2-43254b118569c12bdf614f7822907b49aa0713b6.tar.gz lvm2-43254b118569c12bdf614f7822907b49aa0713b6.tar.xz lvm2-43254b118569c12bdf614f7822907b49aa0713b6.zip |
Thin extend lvcreate man page about snapshot support
-rw-r--r-- | man/lvcreate.8.in | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/man/lvcreate.8.in b/man/lvcreate.8.in index 8f6127a8..e8520d99 100644 --- a/man/lvcreate.8.in +++ b/man/lvcreate.8.in @@ -81,9 +81,7 @@ lvcreate \- create a logical volume in an existing volume group .RB [ \-n | \-\-name .IR SnapshotLogicalVolume { Name | Path }] .BR \-s | \-\-snapshot -.RI { OriginalLogicalVolume { Name | Path } -| -.IR VolumeGroup { Name | Path } +.RI {[ VolumeGroup { Name | Path }/] OriginalLogicalVolumeName .BR \-V | \-\-virtualsize .IR VirtualSize [ bBsSkKmMgGtTpPeE ]} .br @@ -241,16 +239,19 @@ a suitable value automatically. A mirror is divided into regions of this size (in MB), and the mirror log uses this granularity to track which regions are in sync. .TP -.IR \fB\-s ", " \fB\-\-snapshot " " OriginalLogicalVolume { Name | Path } -.RI "| " VolumeGroup { Name | Path } +.IR \fB\-s ", " \fB\-\-snapshot " " OriginalLogicalVolume { Name | Path } Create a snapshot logical volume (or snapshot) for an existing, so called original logical volume (or origin). Snapshots provide a 'frozen image' of the contents of the origin while the origin can still be updated. They enable consistent -backups and online recovery of removed/overwritten data/files. The snapshot -does not need the same amount of storage the origin has. In a typical scenario, -15-20% might be enough. In case the snapshot runs out of storage, use +backups and online recovery of removed/overwritten data/files. +Thin snapshot is created when the origin is a thin volume and +the size is not specified. Thin snapshot shares same blocks within +the thin pool volume. +The snapshot with the specified size does not need the same amount of +storage the origin has. In a typical scenario, 15-20% might be enough. +In case the snapshot runs out of storage, use .BR lvextend (8) to grow it. Shrinking a snapshot is supported by .BR lvreduce (8) |