[install-guide/f21-branch: 16/32] Adding the LVM appendix + removing more TODOs
pbokoc
pbokoc at fedoraproject.org
Tue Dec 9 17:31:47 UTC 2014
commit 865f0d102d883f74cb30c14e9e383d99510a8031
Author: Petr Bokoc <pbokoc at redhat.com>
Date: Mon Dec 8 15:08:13 2014 +0100
Adding the LVM appendix + removing more TODOs
en-US/CustomSpoke_FileSystems.xml | 2 +-
en-US/CustomSpoke_RecommendedScheme.xml | 2 +-
en-US/Disk_Partitions.xml | 2 +-
en-US/Installation_Guide.xml | 1 +
en-US/Understanding_LVM.xml | 28 ++++++++++++++++++++++++++++
5 files changed, 32 insertions(+), 3 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index a9f4424..e28c539 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -23,7 +23,7 @@
</listitem>
<listitem>
<para>
- <guilabel>LVM</guilabel> - Choosing <guilabel>LVM</guilabel> as the <guilabel>Device Type</guilabel> creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see <xref linkend="sect-installation-gui-manual-partitioning-lvm" />. <remark>TODO: xref to the LVM appendix</remark>
+ <guilabel>LVM</guilabel> - Choosing <guilabel>LVM</guilabel> as the <guilabel>Device Type</guilabel> creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see <xref linkend="sect-installation-gui-manual-partitioning-lvm" />. Also see <xref linkend="appe-lvm-overview" /> for some additional information about LVM in general.
</para>
</listitem>
<listitem>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index b103fed..ca5796c 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -199,7 +199,7 @@
</para>
<note>
<para>
- Only assign storage capacity to those partitions you require immediately. You may allocate free space at any time, to meet needs as they occur. <remark>TODO: xref to the LVM appendix</remark>
+ Only assign storage capacity to those partitions you require immediately. You may allocate free space at any time, to meet needs as they occur.
</para>
</note>
<para>
diff --git a/en-US/Disk_Partitions.xml b/en-US/Disk_Partitions.xml
index e5250af..b917bd3 100644
--- a/en-US/Disk_Partitions.xml
+++ b/en-US/Disk_Partitions.xml
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
%BOOK_ENTITIES;
]>
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
index 0c4b2d4..d92c565 100644
--- a/en-US/Installation_Guide.xml
+++ b/en-US/Installation_Guide.xml
@@ -47,6 +47,7 @@
</partintro>
<xi:include href="Kickstart_Syntax_Reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Disk_Partitions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Understanding_LVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/en-US/Understanding_LVM.xml b/en-US/Understanding_LVM.xml
new file mode 100644
index 0000000..16bcfd0
--- /dev/null
+++ b/en-US/Understanding_LVM.xml
@@ -0,0 +1,28 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<appendix id="appe-lvm-overview">
+ <title>Understanding LVM</title>
+ <para>
+ LVM (Logical Volume Management) partitions provide a number of advantages over standard partitions. LVM partitions are formatted as <firstterm>physical volumes</firstterm>. One or more physical volumes are combined to form a <firstterm>volume group</firstterm>. Each volume group's total storage is then divided into one or more <firstterm>logical volumes</firstterm>. The logical volumes function much like standard partitions. They have a file system type, such as <systemitem class="filesystem">ext4</systemitem>, and a mount point.
+ </para>
+ <important>
+ <para>
+ The boot loader cannot read LVM volumes. You must make a standard, non-LVM disk partition for your <filename class="partition">/boot</filename> partition.
+ </para>
+ <para>
+ By default, the installation process always creates the <filename class="partition">/</filename> and <filename class="partition">swap</filename> partitions within LVM volumes, with a separate <filename>/boot</filename> on a standard partition. See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for details.
+ </para>
+ </important>
+ <para>
+ To understand LVM better, imagine the physical volume as a pile of <firstterm>blocks</firstterm>. A block is a storage unit used to store data. Several piles of blocks can be combined to make a much larger pile, just as physical volumes are combined to make a volume group. The resulting pile can be subdivided into several smaller piles of arbitrary size, just as a volume group is allocated to several logical volumes.
+ </para>
+ <para>
+ An administrator may grow or shrink logical volumes without destroying data, unlike standard disk partitions. If the physical volumes in a volume group are on separate drives or RAID arrays then administrators may also spread a logical volume across the storage devices.
+ </para>
+ <para>
+ You may lose data if you shrink a logical volume to a smaller capacity than the data on the volume requires. To ensure maximum flexibility, create logical volumes to meet your current needs, and leave excess storage capacity unallocated. You may safely grow logical volumes to use unallocated space, as your needs dictate.
+ </para>
+</appendix>
\ No newline at end of file
More information about the docs-commits
mailing list