commit cd5c32ea00e4644d0a0e2d825af69ff06062c142
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 17:37:41 2014 +0100
RAID needs multiple disks, not just partitions
en-US/CustomSpoke_FileSystems.xml | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 56544fc..87650fc 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -26,7 +26,7 @@
<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>
+ <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.
</para>
@@ -92,32 +92,32 @@
<title>Software RAID Types</title>
<listitem>
<para>
- <guilabel>RAID0 (Performance)</guilabel> - Distributes data
across multiple disks. Level 0 RAIDs offer increased performance over standard partitions,
and can be used to pool the storage of multiple disks into one large virtual device. Note
that Level 0 RAIDs offer no redundancy, and that the failure of one device in the array
destroys data in the entire array. RAID 0 requires at least two RAID partitions.
+ <guilabel>RAID0 (Performance)</guilabel> - Distributes data
across multiple disks. Level 0 RAID offers increased performance over standard partitions,
and can be used to pool the storage of multiple disks into one large virtual device. Note
that Level 0 RAIDs offer no redundancy, and that the failure of one device in the array
destroys data in the entire array. RAID 0 requires at least two disks.
</para>
</listitem>
<listitem>
<para>
- <guilabel>RAID1 (Redundancy)</guilabel> - Mirrors all data on
one disk onto one or more other disks. Additional devices in the array provide increasing
levels of redundancy. RAID 1 requires at least two RAID partitions.
+ <guilabel>RAID1 (Redundancy)</guilabel> - Mirrors all data on
one disk onto one or more other disks. Additional devices in the array provide increasing
levels of redundancy. RAID 1 requires at least two disks.
</para>
</listitem>
<listitem>
<para>
- <guilabel>RAID4 (Error Checking)</guilabel> - Distributes
data across multiple disks, and uses one disk in the array to store parity information
that safeguards the array in case any disk within the array fails. Because all parity
information is stored on one disk, access to this disk creates a bottleneck in the
performance of the array. RAID 4 requires at least three RAID partitions.
+ <guilabel>RAID4 (Error Checking)</guilabel> - Distributes
data across multiple disks, and uses one disk in the array to store parity information
which safeguards the array in case any disk within the array fails. Because all parity
information is stored on one disk, access to this disk creates a "bottleneck" in
the array's performance. Level 4 RAID requires at least three disks.
</para>
</listitem>
<listitem>
<para>
- <guilabel>RAID5 (Distributed Error Checking)</guilabel> -
Distributes data and parity information across multiple disks. Level 5 RAIDs therefore
offer the performance advantages of distributing data across multiple disks, but do not
share the performance bottleneck of level 4 RAIDs because the parity information is also
distributed through the array. RAID 5 requires at least three RAID partitions.
+ <guilabel>RAID5 (Distributed Error Checking)</guilabel> -
Distributes data and parity information across multiple disks. Level 5 RAIDs therefore
offer the performance advantages of distributing data across multiple disks, but do not
share the performance bottleneck of level 4 RAIDs because the parity information is also
distributed through the array. RAID 5 requires at least three disks.
</para>
</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 disks.
</para>
</listitem>
<listitem>
<para>
- <guilabel>RAID10 (Performance, Redundancy)</guilabel> - Level
10 RAIDs are nested RAIDs or hybrid RAIDs. They are constructed by distributing data over
mirrored sets of disks. For example, a level 10 RAID array constructed from four RAID
partitions consists of two mirrored pairs of striped partitions. RAID 10 requires at least
four RAID partitions.
+ <guilabel>RAID10 (Performance, Redundancy)</guilabel> - Level
10 RAIDs are nested RAIDs or hybrid RAIDs. They are constructed by distributing data over
mirrored sets of disks. For example, a level 10 RAID array constructed from four RAID
partitions consists of two mirrored pairs of striped partitions. RAID 10 requires at least
four disks.
</para>
</listitem>
</itemizedlist>
Show replies by date