commit c26202fb18631aa092734aa0d35cc96c9396d705
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 17:33:09 2014 +0100
More issues in File Systems
en-US/CustomSpoke_FileSystems.xml | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index bbb0003..56544fc 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -18,17 +18,17 @@
<title>Device Types</title>
<listitem>
<para>
- <guilabel>Standard Partition</guilabel> - A standard
partition can contain a file system or swap space, or it can provide a container for
software RAID or an LVM physical volume. Commonly used for <filename
class="directory">/boot</filename>, BIOS Boot and EFI System
partitions. <remark>TODO: xref to the disk partitioning appendix</remark>
+ <guilabel>Standard Partition</guilabel> - A standard
partition can contain a file system or swap space. Standard partitions are most commonly
used for <filename class="directory">/boot</filename>, BIOS Boot and
EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most
other uses. <remark>TODO: xref to the disk partitioning appendix</remark>
</para>
</listitem>
<listitem>
<para>
- <guilabel>LVM</guilabel> - Creating an LVM partition
automatically generates an LVM logical volume. LVM can improve performance when using
physical disks. 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" />.
<remark>TODO: xref to the LVM appendix</remark>
</para>
</listitem>
<listitem>
<para>
- <guilabel>LVM Thin Provisioning</guilabel> - Using thin
provisioning, you can manage a storage pool of free space, known as a
<firstterm>thin pool</firstterm>, which can be allocated to an arbitrary
number of devices when needed by applications. The thin pool can be expanded dynamically
when needed for cost-effective allocation of storage space.
+ <guilabel>LVM Thin Provisioning</guilabel> - Using thin
provisioning, you can manage a storage pool of free space, known as a
<firstterm>thin pool</firstterm>, which can be allocated to an arbitrary
number of devices when needed by applications. The thin pool can be expanded dynamically
when needed for cost-effective allocation of storage space.
</para>
</listitem>
<listitem>
@@ -51,7 +51,7 @@
</listitem>
<listitem>
<para>
- <guilabel>ext3</guilabel> - The ext3 file system is based on
the ext2 file system and has one main advantage - journaling. Using a journaling file
system reduces time spent recovering a file system after a crash as there is no need to
check the file system for metadata consistency by running the
<command>fsck</command> utility every time a crash occurs.
+ <guilabel>ext3</guilabel> - The ext3 file system is based on
the ext2 file system and has one main advantage - journaling. Using a journaling file
system reduces time spent recovering a file system after a crash, as there is no need to
check the file system for metadata consistency by running the
<command>fsck</command> utility every time a crash occurs.
</para>
</listitem>
<listitem>
@@ -69,7 +69,7 @@
<guilabel>xfs</guilabel> - XFS is a highly scalable,
high-performance file system that supports file systems up to 16 exabytes (approximately
16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and
directory structures containing tens of millions of entries. XFS also supports metadata
journaling, which facilitates quicker crash recovery. The maximum supported size of a
single XFS file system is 500 TB.
</para>
<para>
- Note that the size of an XFS file system can not currently be reduced
without destroying and recreating the file system. If you expect that you will need to
adjust the sizes of your file systems often, using XFS is not recommended as it makes
administration substantially more time-consuming.
+ Note that the size of an XFS file system can not currently be reduced
without destroying and recreating the file system. If you expect that you will need to
adjust the sizes of your file systems often, using XFS is not recommended, as it makes
administration substantially more time-consuming.
</para>
</listitem>
<listitem>
@@ -112,7 +112,7 @@
</listitem>
<listitem>
<para>
- <guilabel>RAID6 (Redundant Error Checking)</guilabel> - Level
6 RAIDs are similar to level 5 RAIDs, but instead of storing only one set of parity data,
they store two sets. RAID 6 requires at least four RAID partitions.
+ <guilabel>RAID6 (Redundant Error Checking)</guilabel> - Level
6 RAIDs are similar to level 5 RAIDs, but instead of storing only one set of parity data,
they store two sets. RAID 6 requires at least four RAID partitions.
</para>
</listitem>
<listitem>
Show replies by date