[install-guide/f21-branch] Additional grammar fixes in CustomSpoke
by pbokoc
commit bcbbf5001b3f38c23d9bbeb869aea95eed9d49ee
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 21:56:52 2014 +0100
Additional grammar fixes in CustomSpoke
en-US/CustomSpoke_FileSystems.xml | 12 ++++++------
en-US/CustomSpoke_RecommendedScheme.xml | 15 +++++++++------
en-US/CustomSpoke_SoftwareRAID.xml | 4 ++--
3 files changed, 17 insertions(+), 14 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 87650fc..2dbe59f 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -9,7 +9,7 @@
&PRODUCT; supports multiple types of devices and file systems. The lists below offer a short description of each available device, file system and RAID type and notes on their usage.
</para>
<para>
- To select a device type or a file system of a partition or a logical volume, select it in the list in <xref linkend="sect-installation-gui-manual-partitioning" /> and select <guilabel>Device Type</guilabel> and a <guilabel>File System</guilabel> from their respective drop-down menus on the right side of the screen. Then, click <guilabel>Update Settings</guilabel> and repeat this process for all mount points you want to modify.
+ To select a device type or a file system of a partition or a logical volume, select it in the list in <xref linkend="sect-installation-gui-manual-partitioning" /> and select a <guilabel>Device Type</guilabel> and a <guilabel>File System</guilabel> from their respective drop-down menus on the right side of the screen. Then, click <guilabel>Update Settings</guilabel> and repeat this process for all mount points you want to modify.
</para>
<para>
To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when creating or modifying a Btrfs volume or LVM volume group, or select <guilabel>Software RAID</guilabel> as the device type to create software RAID with standard partitions. For detailed instructions, see <xref linkend="sect-installation-gui-manual-partitioning-btrfs" />, <xref linkend="sect-installation-gui-manual-partitioning-lvm" />, and <xref linkend="sect-installation-gui-manual-partitioning-swraid" /> as needed.
@@ -18,12 +18,12 @@
<title>Device Types</title>
<listitem>
<para>
- <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>
+ <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> and the 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> - 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" />. <remark>TODO: xref to the LVM appendix</remark>
</para>
</listitem>
<listitem>
@@ -92,17 +92,17 @@
<title>Software RAID Types</title>
<listitem>
<para>
- <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.
+ <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 disks.
+ <guilabel>RAID1 (Redundancy)</guilabel> - Mirrors all data from one partition 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 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.
+ <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>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index cb72e93..7cd1fcc 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -13,11 +13,14 @@
<term><filename class="directory">/boot</filename> - 500 MB</term>
<listitem>
<para>
- This partition contains the operating system kernel, which allows &PRODUCT; to boot. It also contains other files used during the bootstrap process. Due to the limitations of most firmwares, creating a small partition to hold these is recommended. In most scenarios, a 500 MB <filename class="directory">/boot</filename> partition is adequate.
+ This partition contains the operating system kernel, which allows &PRODUCT; to boot. It also contains other files used during the bootstrap process. Due to the limitations of most firmware, creating a separate, small standard partition for this directory is recommended. In most scenarios, a 500 MB <filename class="directory">/boot</filename> partition is adequate.
</para>
<important>
<para>
- If your system has a hardware RAID controller, be aware that some BIOS types do not support booting from the it. In that case, the <filename class="directory">/boot</filename> partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
+ If your system has a hardware RAID controller, be aware that some BIOS types do not support booting from it. In that case, the <filename class="directory">/boot</filename> partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
+ </para>
+ <para>
+ Also note that the <filename class="directory">/boot</filename> can not be placed on a LVM logical volume or a Btrfs subvolume. Use a standard partition.
</para>
</important>
</listitem>
@@ -42,7 +45,7 @@
<term><filename class="directory">/home</filename> - at least 1 GB</term>
<listitem>
<para>
- To store user data separately from system data, create a dedicated partition within a volume group for the /home directory. This partition should be sized based on the amount of data that will be stored locally, number of users, and so on. This will allow you to upgrade or reinstall &PRODUCT; without erasing user data files. During the installation, a separate <filename class="directory">/home</filename> partition will be created if there is 50 GB or more free space for your &PRODUCT; installation.
+ To store user data separately from system data, create a dedicated partition within a volume group for the /home directory. This partition should be sized based on the amount of data that will be stored locally, number of users, and so on. This will allow you to upgrade or reinstall &PRODUCT; without erasing user data files. During the installation, a separate <filename class="directory">/home</filename> partition will be created if there are 50 GB or more free space for your &PRODUCT; installation.
</para>
</listitem>
</varlistentry>
@@ -184,10 +187,10 @@
<para>
If your system requires either a BIOS Boot partition or an EFI System Partition based on the requirements detailed above, this partition must be created as a standard physical partition. It can not reside on an LVM volume or a Btrfs subvolume.
</para>
+ <para>
+ Also note that if your system does not require any of these partitions, they will not be shown in the <guilabel>File System</guilabel> menu in mount point options.
+ </para>
</important>
- <para>
- Also note that you will only be created a BIOS Boot or an EFI System Partition file system if your system actually requires it. Otherwise, they will not be available in the
- </para>
</listitem>
</varlistentry>
</variablelist>
diff --git a/en-US/CustomSpoke_SoftwareRAID.xml b/en-US/CustomSpoke_SoftwareRAID.xml
index 0d952d0..33a7654 100644
--- a/en-US/CustomSpoke_SoftwareRAID.xml
+++ b/en-US/CustomSpoke_SoftwareRAID.xml
@@ -9,7 +9,7 @@
<firstterm>Redundant arrays of independent disks</firstterm> (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. See <xref linkend="sect-installation-gui-manual-partitioning-filesystems" /> a description of different kinds of RAIDs.
</para>
<para>
- A RAID device is created in one step and disks are added or removed as necessary. One RAID partition per physical disk is allowed for each device, so the number of disks available to the installation program determines which levels of RAID device are available to you. For example, if your system has two hard drives, the installation program will not allow you to create a RAID10 device, which requires 4 separate partitions.
+ A RAID device is created in one step, and disks are added or removed as necessary. One RAID partition per physical disk is allowed for each device, so the number of disks available to the installation program determines which levels of RAID device are available to you. For example, if your system has two hard drives, the installation program will not allow you to create a RAID10 device, which requires 4 separate partitions.
</para>
<important>
<para>
@@ -56,7 +56,7 @@
</step>
<step>
<para>
- In the <guilabel>Device(s)</guilabel> section on the right side of the screen, you can see that the partition has been assigned to several. Click the <guilabel>Modify</guilabel> button to configure on which drive this partition will be created.
+ In the <guilabel>Device(s)</guilabel> section on the right side of the screen, you can see that the partition has been assigned to several physical disks. Click the <guilabel>Modify</guilabel> button to configure on which drives this partition will be created.
</para>
</step>
<step>
9 years, 5 months
[networking-guide] master: Bulk add: nbsp to prompts (9d81553)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 9d8155388222e93f8d6c7e88ffd2c03cdc72d57a
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sat Nov 15 11:54:21 2014 +0100
Bulk add: nbsp to prompts
>---------------------------------------------------------------
Diff suppressed because of size. To see it, use:
git diff --patch-with-stat --no-color --find-copies-harder --ignore-space-at-eol ^9d8155388222e93f8d6c7e88ffd2c03cdc72d57a~1 9d8155388222e93f8d6c7e88ffd2c03cdc72d57a
9 years, 5 months
[networking-guide] master: Change NETMASK to PREFIX (b994b51)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit b994b51400bef053cd4cf64267341e527e22c9c3
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sat Nov 15 11:52:29 2014 +0100
Change NETMASK to PREFIX
NETMASK is depreciated
PREFIX is easier to use, less error prone.
See usr/share/doc/initscripts/sysconfig.txt
>---------------------------------------------------------------
en-US/Configure_802_1Q_VLAN_Tagging.xml | 2 +-
en-US/Configure_Network_Bonding.xml | 4 ++--
en-US/Configure_Network_Bridging.xml | 4 ++--
en-US/Configure_Network_Teaming.xml | 2 +-
en-US/Configure_Networking.xml | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml
index 67eb915..da3bcf5 100644
--- a/en-US/Configure_802_1Q_VLAN_Tagging.xml
+++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml
@@ -189,7 +189,7 @@ ONBOOT=yes</screen>
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.1.1
-NETMASK=255.255.255.0
+PREFIX=24
NETWORK=192.168.1.0
VLAN=yes</screen>
<para>
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 85a064c..6fe3ffd 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -364,7 +364,7 @@ See the <filename>modprobe(8)</filename> man page for more command options.
NAME=bond0
TYPE=Bond
IPADDR=192.168.1.1
-NETMASK=255.255.255.0
+PREFIX=24
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS="<replaceable>bonding parameters separated by spaces</replaceable>"</programlisting>
@@ -479,7 +479,7 @@ Then when complete, bring up all the slaves, which will bring up the bond (provi
NAME=bondN
TYPE=Bond
IPADDR=192.168.1.1
-NETMASK=255.255.255.0
+PREFIX=24
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS="<replaceable>bonding parameters separated by spaces</replaceable>"</programlisting>
diff --git a/en-US/Configure_Network_Bridging.xml b/en-US/Configure_Network_Bridging.xml
index f62d74c..237736b 100644
--- a/en-US/Configure_Network_Bridging.xml
+++ b/en-US/Configure_Network_Bridging.xml
@@ -282,7 +282,7 @@ See the <filename>modprobe(8)</filename> man page for more command options.
<programlisting>DEVICE=br0
TYPE=Bridge
IPADDR=192.168.1.1
-NETMASK=255.255.255.0
+PREFIX=24
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
@@ -350,7 +350,7 @@ NM_CONTROLLED=no</programlisting>
ONBOOT=yes
TYPE=Bridge
IPADDR=192.168.1.1
-NETMASK=255.255.255.0
+PREFIX=24
NM_CONTROLLED=no</programlisting>
</para>
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index b90ebd9..5c633be 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -507,7 +507,7 @@ DEVICETYPE=Team
ONBOOT=yes
BOOTPROTO=none
IPADDR=192.168.11.1
-NETMASK=255.255.255.0
+PREFIX=24
TEAM_CONFIG='{"runner": {"name": "activebackup"}, "link_watch": {"name": "ethtool"}}'</screen>
This creates the interface to the team, in other words, this is the master.
</para>
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 680c111..c434640 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -1582,7 +1582,7 @@ To restrict connections and networking, there are two options which can be used
<programlisting>DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
-NETMASK=255.255.255.0
+PREFIX=24
IPADDR=10.0.1.27
NM_CONTROLLED=no</programlisting>
Optionally specify the hardware or MAC address using the <command>HWADDR</command> directive. Note that this will influence the device naming procedure as explained in <xref linkend="ch-Consistent_Network_Device_Naming" />. You do not need to specify the broadcast address as this is calculated automatically by <application>ipcalc</application>.
9 years, 5 months
[install-guide/f21-branch] RAID needs multiple disks, not just partitions
by pbokoc
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>
9 years, 5 months
[install-guide] (3 commits) ...More issues in File Systems
by pbokoc
Summary of changes:
5a96120... Adding remarks to CustomSpoke_FileSystems so we don't forge (*)
5c28de7... Use more xrefs in CustomSpoke_FileSystems (*)
c26202f... More issues in File Systems (*)
(*) This commit already existed in another branch; no separate mail sent
9 years, 5 months
[install-guide/f21-branch] More issues in File Systems
by pbokoc
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>
9 years, 5 months
[install-guide/f21-branch] Use more xrefs in CustomSpoke_FileSystems
by pbokoc
commit 5c28de7b2b9b2036c766093032b163d350c3753e
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 17:14:11 2014 +0100
Use more xrefs in CustomSpoke_FileSystems
en-US/CustomSpoke_FileSystems.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 6d8caac..bbb0003 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -12,7 +12,7 @@
To select a device type or a file system of a partition or a logical volume, select it in the list in <xref linkend="sect-installation-gui-manual-partitioning" /> and select <guilabel>Device Type</guilabel> and a <guilabel>File System</guilabel> from their respective drop-down menus on the right side of the screen. Then, click <guilabel>Update Settings</guilabel> and repeat this process for all mount points you want to modify.
</para>
<para>
- To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when modifying the Btrfs volume or LVM volume group, or select <guilabel>Software RAID</guilabel> as the device type to create software RAID with standard partitions. For detailed steps, see the part of this chapter detailing creating a Btrfs, LVM or software RAID partitioning layout as applicable.
+ To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when creating or modifying a Btrfs volume or LVM volume group, or select <guilabel>Software RAID</guilabel> as the device type to create software RAID with standard partitions. For detailed instructions, see <xref linkend="sect-installation-gui-manual-partitioning-btrfs" />, <xref linkend="sect-installation-gui-manual-partitioning-lvm" />, and <xref linkend="sect-installation-gui-manual-partitioning-swraid" /> as needed.
</para>
<itemizedlist>
<title>Device Types</title>
9 years, 5 months
[install-guide/f21-branch] Adding remarks to CustomSpoke_FileSystems so we don't forget to xref
by pbokoc
commit 5a96120602c16eda14f51ff2d932af2085f1b6ff
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 18 17:06:30 2014 +0100
Adding remarks to CustomSpoke_FileSystems so we don't forget to xref
en-US/CustomSpoke_FileSystems.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 6ab9678..6d8caac 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -18,12 +18,12 @@
<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.
+ <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>
</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" />.
+ <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>
</para>
</listitem>
<listitem>
9 years, 5 months