X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;ds=sidebyside;f=local-lvm.adoc;h=45e875f88e8c1a4c8c89cd61d5b0f633242164aa;hb=a7d40e1f890c14383dddf97eda2e627db34dbac7;hp=999b7bc958abad7aacad881490aa00f491b47e0d;hpb=8b849dc378465dc19efca1d155477b45772191c5;p=pve-docs.git

diff --git a/local-lvm.adoc b/local-lvm.adoc
index 999b7bc..45e875f 100644
--- a/local-lvm.adoc
+++ b/local-lvm.adoc
@@ -1,12 +1,15 @@
 Logical Volume Manager (LVM)
 ----------------------------
 include::attributes.txt[]
+ifdef::wiki[]
+:pve-toplevel:
+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
 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
+the **V**olume **G**roup (VG) `pve`. The following output is from a
 test installation using a small 8GB disk:
 
 ----
@@ -30,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 operation system.
 
 swap:: Swap partition
 
@@ -38,3 +41,20 @@ 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.
 
+Hardware
+~~~~~~~~
+
+We highly recommend to use a hardware RAID controller (with BBU) for
+such setups. This increases performance, provides redundancy, and make
+disk replacements easier (hot-pluggable).
+
+LVM itself does not need any special hardware, and memory requirements
+are very low.
+
+
+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.