summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZdenek Kabelac <zkabelac@redhat.com>2019-01-18 20:28:35 +0100
committerZdenek Kabelac <zkabelac@redhat.com>2019-01-21 12:53:16 +0100
commit01cbdc4e673989c4d432e6bea8cde1f8f9e8cda5 (patch)
tree5ec928cdd1f2e3c93a2576c13fca8374dfa44d83
parenta16d914d34fff420c663ba34ac8dabfc4403de51 (diff)
downloadlvm2-01cbdc4e673989c4d432e6bea8cde1f8f9e8cda5.tar.gz
vdo: man documenting resize
-rw-r--r--man/lvmvdo.7_main36
1 files changed, 36 insertions, 0 deletions
diff --git a/man/lvmvdo.7_main b/man/lvmvdo.7_main
index e789f7f42..11ca3aca9 100644
--- a/man/lvmvdo.7_main
+++ b/man/lvmvdo.7_main
@@ -219,6 +219,42 @@ Note: vdostats currently understands only /dev/mapper device names.
.fi
+.SS 4. Extending VDOPoolLV size
+
+Adding more space to hold VDO data and metadata can be made via
+extension of VDODataLV.
+
+Note: Size of VDOPoolLV cannot be reduced.
+
+.B lvextend -L+AddingSize VG/VDOPoolLV
+
+.I Example
+.br
+.nf
+# lvextend -L+50G vg/vdopool0
+# lvresize -L300G vg/vdopool1
+.fi
+
+.SS 4. Extending or reducing VDOLV size
+
+VDO LV can be extended or reduced as standard LV.
+
+Note: Reduction needs to process TRIM for reduced disk area
+to unmap used data blocks from VDOPoolLV and it may take
+a long time.
+
+.B lvextend -L+AddingSize VG/VDOLV
+.B lvreduce -L-ReducingSize VG/VDOLV
+
+.I Example
+.br
+.nf
+# lvextend -L+50G vg/vdo0
+# lvreduce -L-50G vg/vdo1
+# lvresize -L200G vg/vdo2
+.fi
+
+
.SH VDO Topics
.br