totp: fix copy/paste mistake

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

diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
index b4a278c6d00d009dd6042f13e2a8969deac80bb6..487aac61a60f5888d71245eb2a449e7ed1dc654d 100644 (file)
--- a/pve-storage-lvm.adoc
+++ b/pve-storage-lvm.adoc
@@ -1,10 +1,14 @@
+[[storage_lvm]]
 LVM Backend
 -----------
-include::attributes.txt[]
+ifdef::wiki[]
+:pve-toplevel:
+:title: Storage: LVM
+endif::wiki[]
 
 Storage pool type: `lvm`
 
-LVM is a thin software layer on top of hard disks and partitions. It
+LVM is a light software layer on top of hard disks and partitions. It
 can be used to split available disk space into smaller logical
 volumes. LVM is widely used on Linux and makes managing hard drives
 easier.
@@ -14,6 +18,7 @@ can easily manage space on that iSCSI LUN, which would not be possible
 otherwise, because the iSCSI specification does not define a
 management interface for space allocation.
 
+
 Configuration
 ~~~~~~~~~~~~~
 
@@ -32,14 +37,17 @@ on a remote iSCSI server.
 
 `saferemove`::
 
-Zero-out data when removing LVs. When removing a volume, this makes
-sure that all data gets erased.
+Called "Wipe Removed Volumes" in the web UI. Zero-out data when removing LVs.
+When removing a volume, this makes sure that all data gets erased and cannot be
+accessed by other LVs created later (which happen to be assigned the same
+physical extents). This is a costly operation, but may be required as a security
+measure in certain environments.
 
 `saferemove_throughput`::
 
-Wipe throughput ('cstream -t' parameter value).
+Wipe throughput (`cstream -t` parameter value).
 
-.Configuration Example ('/etc/pve/storage.cfg')
+.Configuration Example (`/etc/pve/storage.cfg`)
 ----
 lvm: myspace
        vgname myspace
@@ -58,15 +66,15 @@ Storage Features
 ~~~~~~~~~~~~~~~~
 
 LVM is a typical block storage, but this backend does not support
-snapshot and clones. Unfortunately, normal LVM snapshots are quite
-inefficient, because they interfere all writes on the whole volume
+snapshots and clones. Unfortunately, normal LVM snapshots are quite
+inefficient, because they interfere with all writes on the entire volume
 group during snapshot time.
 
 One big advantage is that you can use it on top of a shared storage,
-for example an iSCSI LUN. The backend itself implement proper cluster
-wide locking.
+for example, an iSCSI LUN. The backend itself implements proper cluster-wide
+locking.
 
-TIP: The newer LVM-thin backend allows snapshot and clones, but does
+TIP: The newer LVM-thin backend allows snapshots and clones, but does
 not support shared storage.
 
 
@@ -84,5 +92,13 @@ List available volume groups:
 
  # pvesm lvmscan
 
+ifdef::wiki[]
+
+See Also
+~~~~~~~~
+
+* link:/wiki/Storage[Storage]
+
+endif::wiki[]