vzdump: drop overly scary & outdated warning about fleecing

[pve-docs.git] / local-lvm.adoc

diff --git a/local-lvm.adoc b/local-lvm.adoc
index 7c2a6cea9a0b4507bde5a540ce56dabdaf39fa00..b6009c8c0e66ac002fb71e329aace56c229a8d00 100644 (file)
--- a/local-lvm.adoc
+++ b/local-lvm.adoc
@@ -1,3 +1,4 @@
+[[chapter_lvm]]
 Logical Volume Manager (LVM)
 ----------------------------
 ifdef::wiki[]
@@ -6,7 +7,7 @@ endif::wiki[]
 
 Most people install {pve} directly on a local disk. The {pve}
 installation CD offers several options for local disk management, and
-the current default setup uses LVM. The installer let you select a
+the current default setup uses LVM. The installer lets you select a
 single disk for such setup, and uses that disk as physical volume for
 the **V**olume **G**roup (VG) `pve`. The following output is from a
 test installation using a small 8GB disk:
@@ -32,7 +33,7 @@ VG:
   swap pve  -wi-ao---- 896.00m     
 ----
 
-root:: Formatted as `ext4`, and contains the operation system.
+root:: Formatted as `ext4`, and contains the operating system.
 
 swap:: Swap partition
 
@@ -40,10 +41,11 @@ data:: This volume uses LVM-thin, and is used to store VM
 images. LVM-thin is preferable for this task, because it offers
 efficient support for snapshots and clones.
 
-For {pve} versions up to 4.1, the installer creates a Logical Volume
-called ``data'' which is mounted at `/var/lib/vz`
-Starting from 4.2 the Logical Volume ``data'' is a LVM thin volume, used
-for block based storage of guest systems, and `/var/lib/vz` is simply a
+For {pve} versions up to 4.1, the installer creates a standard logical
+volume called ``data'', which is mounted at `/var/lib/vz`.
+
+Starting from version 4.2, the logical volume ``data'' is a LVM-thin pool,
+used to store block based guest images, and `/var/lib/vz` is simply a
 directory on the root file system.
 
 Hardware
@@ -62,25 +64,32 @@ Bootloader
 
 We install two boot loaders by default. The first partition contains
 the standard GRUB boot loader. The second partition is an **E**FI **S**ystem
-**P**artition (ESP), which makes it possible to boot on EFI systems.
+**P**artition (ESP), which makes it possible to boot on EFI systems and to
+apply xref:sysadmin_firmware_persistent[persistent firmware updates] from the
+user space.
 
 
 Creating a Volume Group
 ~~~~~~~~~~~~~~~~~~~~~~~
 
 Let's assume we have an empty disk `/dev/sdb`, onto which we want to
-create a Volume Group named ``vmdata''.
+create a volume group named ``vmdata''.
+
+CAUTION: Please note that the following commands will destroy all
+existing data on `/dev/sdb`.
 
 First create a partition.
 
  # sgdisk -N 1 /dev/sdb
 
-Create a **P**hysical **V**olumes (PV) without confirmation and 250K
+
+Create a **P**hysical **V**olume (PV) without confirmation and 250K
 metadatasize.
 
  # pvcreate --metadatasize 250k -y -ff /dev/sdb1
 
-Create a **V**olume **G**roup (VG) named ``vmdata'' on `/dev/sdb1`
+
+Create a volume group named ``vmdata'' on `/dev/sdb1`
 
  # vgcreate vmdata /dev/sdb1
 
@@ -98,11 +107,12 @@ A real world example:
 
 Now a filesystem must be created on the LV.
 
- # mkfs.ext4 /dev/data/vz
+ # mkfs.ext4 /dev/pve/vz
 
 At last this has to be mounted.
 
-WARNING: be sure that `/var/lib/vz` is empty. On a default installation it's not.
+WARNING: be sure that `/var/lib/vz` is empty. On a default
+installation it's not.
 
 To make it always accessible add the following line in `/etc/fstab`.
 
@@ -112,17 +122,18 @@ To make it always accessible add the following line in `/etc/fstab`.
 Resizing the thin pool
 ~~~~~~~~~~~~~~~~~~~~~~
 
-NOTE: When extending the data pool, the metadata pool must be extended with it.
-
-Resize the LV and the metadata pool can be achieved with the following command.
+Resize the LV and the metadata pool with the following command:
 
  # lvresize --size +<size[\M,G,T]> --poolmetadatasize +<size[\M,G]> <VG>/<LVThin_pool>
 
+NOTE: When extending the data pool, the metadata pool must also be
+extended.
+
 
-Create a LVM-Thin pool
+Create a LVM-thin pool
 ~~~~~~~~~~~~~~~~~~~~~~
 
 A thin pool has to be created on top of a volume group.
-How to create a Volume Group see Section LVM.
+How to create a volume group see Section LVM.
 
  # lvcreate -L 80G -T -n vmstore vmdata