[install-guide/f21-branch] Small adjustments in LVM configuration in Manual Partitioning
by pbokoc
commit b30eafc6edd5d9272ba143e2dcb1f571e7610122
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 20:07:13 2014 +0100
Small adjustments in LVM configuration in Manual Partitioning
en-US/CustomSpoke_AddLVM.xml | 27 ++++++++++++++++++++-------
1 files changed, 20 insertions(+), 7 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
index cb85428..cc73db8 100644
--- a/en-US/CustomSpoke_AddLVM.xml
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -6,16 +6,16 @@
<section id="sect-installation-gui-manual-partitioning-lvm">
<title>Creating a Logical Volume Managament (LVM) Layout</title>
<para>
- <firstterm>Logical Volume Management</firstterm> (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as <firstterm>physical volumes</firstterm> that can be grouped together into <firstterm>volume groups</firstterm>. Each volume group can be divided into multiple <firstterm>logical volumes</firstterm>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks.
+ <firstterm>Logical Volume Management</firstterm> (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as <firstterm>physical volumes</firstterm> that can be grouped together into <firstterm>volume groups</firstterm>. Each volume group can be divided into multiple <firstterm>logical volumes</firstterm>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions which can span multiple physical disks.
</para>
<para>
<remark>TODO: xref to the LVM appendix</remark>
</para>
- <important>
+ <warning>
<para>
- During text-mode installation, manual LVM configuration is not available. You can switch to a shell as described in <xref linkend="sect-consoles-logs-during-installation" /> and use the <command>pvcreate</command>, <command>vgcreate</command> and <command>lvcreate</command> commands, or you can use a Kickstart file. See <xref linkend="chap-kickstart-installations" /> for information about Kickstart installations.
+ Some partition types - notably the <filename class="directory">/boot</filename> directory and the BIOS Boot and EFI partitions - can not be placed on logical volumes. Use standard physical volumes for them. See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information.
</para>
- </important>
+ </warning>
<para>
<remark>TODO: screen</remark>
</para>
@@ -36,7 +36,7 @@
</step>
<step>
<para>
- The mount point has now been created using the default settings, which means it has been created as a logical volume, and a volume group has been created to contain it. Click the newly created mount point in the left pane to configure it further.
+ The mount point has now been created using the default settings, which means it has been created as an LVM logical volume, and a volume group has been created to contain it. Select the newly created mount point in the left pane to configure it further. If you want to use thin provisioning for this volume, change the <guilabel>Device Type</guilabel> option to <guilabel>LVM Thin Provisioning</guilabel>.
</para>
</step>
<step>
@@ -48,6 +48,11 @@
<para>
In the <guilabel>Configure Volume Group</guilabel> dialog, you can change the volume group's name, its <guilabel>RAID level</guilabel> (see <xref linkend="sect-installation-gui-manual-partitioning-swraid" /> for details about software RAID), and you can also specify which physical devices (disks) this volume group should reside on. You can select one or more disks which will be used to hold this volume group by holding down <keycap>Ctrl</keycap> and clicking each disk in the list.
</para>
+ <note>
+ <para>
+ If you select a redundant RAID type (such as <guilabel>RAID1 (Redundancy)</guilabel>), the volume group will take up twice its actual size on your disks. A 5 GB volume group with RAID1 will take up 10 GB of space.
+ </para>
+ </note>
<para>
You can also make sure that the volume group is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume group. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for information about LUKS disk encryption.
</para>
@@ -57,10 +62,15 @@
<para>
After you finish configuring the volume group settings, click <guilabel>Save</guilabel> to return to the main <guilabel>Manual Partitioning</guilabel> screen.
</para>
+ <note>
+ <para>
+ The configuration dialog does not allow you to specify the size of the volume group's <firstterm>physical extents</firstterm>. The size will always be set to the default value of 4 MiB. If you want to create a volume group with different physical extents, create it manually by switching to an interactive shell and using the <command>vgcreate</command> command, or use a Kickstart file with the <command>volgroup --pesize=<replaceable>size</replaceable></command> command.
+ </para>
+ </note>
</step>
<step>
<para>
- If you need to create more than one volume group, open the <guilabel>Volume Group</guilabel> drop-down menu, and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step; again, select a name, storage devices, encryption settings, RAID level and size policy for the new group, and click <guilabel>Save</guilabel>. The new volume group will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing logical volumes and change this setting to assign them to a different volume group.
+ If you need to create more than one volume group, open the <guilabel>Volume Group</guilabel> drop-down menu, and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step; again, select a name, storage devices, encryption settings, RAID level and size policy for the new group, and click <guilabel>Save</guilabel>. The new volume group will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing mount points and change this setting to assign them to a different volume group.
</para>
</step>
<step>
@@ -70,6 +80,9 @@
</step>
</procedure>
<para>
- Repeat this procedure for any additional logical volumes you want to create. Note that when creating additional LVM logical volumes, a new volume group is not automatically created; instead, any additional volumes are assigned to an existing group. For each volume you create, review its settings and make sure that it is assigned to the correct group, that it has a reasonable size, and that it has a descriptive name so you can identify the volume later if you need to.
+ Repeat this procedure for any additional logical volumes you want to create. Note that when creating additional LVM logical volumes, a new volume group is not automatically created each time; instead, any additional volumes are assigned to an existing group.
+ </para>
+ <para>
+ For each mount point you create, review its settings and make sure that it is assigned to the correct group, that it has a sufficient capacity, and that it has a descriptive name so you can identify the volume later if you need to.
</para>
</section>
9 years, 5 months
[install-guide/f21-branch] Adding a procedure for LVM creation to CustomSpoke
by pbokoc
commit 0f0e0a74e93a1e38f7b9e17cc7269d8439533c2b
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 19:23:53 2014 +0100
Adding a procedure for LVM creation to CustomSpoke
en-US/CustomSpoke_AddLVM.xml | 66 +++++++++++++++++++++++++++++++++++++++++-
1 files changed, 65 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
index 934b029..cb85428 100644
--- a/en-US/CustomSpoke_AddLVM.xml
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -6,6 +6,70 @@
<section id="sect-installation-gui-manual-partitioning-lvm">
<title>Creating a Logical Volume Managament (LVM) Layout</title>
<para>
- text
+ <firstterm>Logical Volume Management</firstterm> (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as <firstterm>physical volumes</firstterm> that can be grouped together into <firstterm>volume groups</firstterm>. Each volume group can be divided into multiple <firstterm>logical volumes</firstterm>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks.
+ </para>
+ <para>
+ <remark>TODO: xref to the LVM appendix</remark>
+ </para>
+ <important>
+ <para>
+ During text-mode installation, manual LVM configuration is not available. You can switch to a shell as described in <xref linkend="sect-consoles-logs-during-installation" /> and use the <command>pvcreate</command>, <command>vgcreate</command> and <command>lvcreate</command> commands, or you can use a Kickstart file. See <xref linkend="chap-kickstart-installations" /> for information about Kickstart installations.
+ </para>
+ </important>
+ <para>
+ <remark>TODO: screen</remark>
+ </para>
+ <para>
+ Follow the procedure below to create LVM logical volumes and volume groups.
+ </para>
+ <procedure>
+ <title>Creating LVM Logical Volumes and Groups</title>
+ <step>
+ <para>
+ Click the <guilabel>+</guilabel> button at the bottom of the list showing existing mount points. A new dialog window will open.
+ </para>
+ </step>
+ <step>
+ <para>
+ In the new dialog window, specify a mount point you want to create a separate logical volume for - for example, <filename class="directory">/</filename>. Optionally, specify a size for the volume using standard units such as MB or GB (for example, <literal>50GB</literal>). Then, click <guilabel>Add mount point</guilabel> to add the volume and return to the main partitioning screen.
+ </para>
+ </step>
+ <step>
+ <para>
+ The mount point has now been created using the default settings, which means it has been created as a logical volume, and a volume group has been created to contain it. Click the newly created mount point in the left pane to configure it further.
+ </para>
+ </step>
+ <step>
+ <para>
+ In the <guilabel>Volume Group</guilabel> menu, you can see that the volume has been assigned to an automatically created volume group, which is named after the &PRODUCT; variant you are installing (for example, <literal>fedora-server</literal>. Click the <guilabel>Modify</guilabel> button under the drop-down menu to access the volume group settings.
+ </para>
+ </step>
+ <step>
+ <para>
+ In the <guilabel>Configure Volume Group</guilabel> dialog, you can change the volume group's name, its <guilabel>RAID level</guilabel> (see <xref linkend="sect-installation-gui-manual-partitioning-swraid" /> for details about software RAID), and you can also specify which physical devices (disks) this volume group should reside on. You can select one or more disks which will be used to hold this volume group by holding down <keycap>Ctrl</keycap> and clicking each disk in the list.
+ </para>
+ <para>
+ You can also make sure that the volume group is encrypted by selecting the <guilabel>Encrypt</guilabel> option; this will enable LUKS encryption for the entire volume group. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for information about LUKS disk encryption.
+ </para>
+ <para>
+ Additionally, you can set a fixed size for the volume group by selecting the <guilabel>Fixed</guilabel> option from the <guilabel>Size policy</guilabel> menu, and entering a size for the volume group.
+ </para>
+ <para>
+ After you finish configuring the volume group settings, click <guilabel>Save</guilabel> to return to the main <guilabel>Manual Partitioning</guilabel> screen.
+ </para>
+ </step>
+ <step>
+ <para>
+ If you need to create more than one volume group, open the <guilabel>Volume Group</guilabel> drop-down menu, and select the <guilabel>Create a new volume group</guilabel> option. A new dialog window will open, identical to the one described in the previous step; again, select a name, storage devices, encryption settings, RAID level and size policy for the new group, and click <guilabel>Save</guilabel>. The new volume group will then become available in the <guilabel>Volume Group</guilabel> drop-down menu; you can then go through your existing logical volumes and change this setting to assign them to a different volume group.
+ </para>
+ </step>
+ <step>
+ <para>
+ Configure other settings specific to the logical volume - its <guilabel>Mount Point</guilabel>, <guilabel>Desired Capacity</guilabel>, <guilabel>File System</guilabel>, and <guilabel>Name</guilabel>. Press <guilabel>Update Settings</guilabel> to apply any changes to the configuration.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ Repeat this procedure for any additional logical volumes you want to create. Note that when creating additional LVM logical volumes, a new volume group is not automatically created; instead, any additional volumes are assigned to an existing group. For each volume you create, review its settings and make sure that it is assigned to the correct group, that it has a reasonable size, and that it has a descriptive name so you can identify the volume later if you need to.
</para>
</section>
9 years, 5 months
[install-guide/f21-branch] Updating remark in CustomSpoke I don't forget what I wanted
by pbokoc
commit a8c5277909bc676ea1401b3d8493c95889f6282d
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 18:56:05 2014 +0100
Updating remark in CustomSpoke I don't forget what I wanted
en-US/CustomSpoke.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml
index b44aaa5..90d61c0 100644
--- a/en-US/CustomSpoke.xml
+++ b/en-US/CustomSpoke.xml
@@ -58,7 +58,7 @@
To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press <guilabel>Rescan Disks</guilabel> and wait until the scanning process completes. Then, press <guilabel>OK</guilabel> to return to <xref linkend="sect-installation-gui-storage-partitioning" />; all detected disks including any new ones will be displayed in the <guilabel>Local Standard Disks</guilabel> section.
</para>
<para>
- <remark>TODO: screen</remark>
+ <remark>TODO: screen of Rescan Disks</remark>
</para>
<para>
After you finish configuring your system storage, press <guilabel>Done</guilabel> in the top left corner to save the configuration and return to the <guilabel>Installation Summary</guilabel> screen. At this point, the installer will check if your storage configuration is valid. If an error was detected, a message will be displayed at the bottom of the screen. Click the message to open a dialog window explaining what kind of error has been detected (for example, you put <filename class="directory">/boot</filename> on a Btrfs subvolume, or you did not create a BIOS Boot partition when your system requires one).
9 years, 5 months
[install-guide/f21-branch] Markup update in FilterSpoke_AddFCoE
by pbokoc
commit 5803e1c427fd2554e4ca24553aab66c7f11b45c7
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 18:51:33 2014 +0100
Markup update in FilterSpoke_AddFCoE
en-US/FilterSpoke_AddFCoE.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/FilterSpoke_AddFCoE.xml b/en-US/FilterSpoke_AddFCoE.xml
index f3c64e2..8af7fc6 100644
--- a/en-US/FilterSpoke_AddFCoE.xml
+++ b/en-US/FilterSpoke_AddFCoE.xml
@@ -26,7 +26,7 @@
</para>
<variablelist>
<varlistentry>
- <term>Use DCB</term>
+ <term><guilabel>Use DCB</guilabel></term>
<listitem>
<para>
<firstterm>Data Center Bridging</firstterm> (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. This option should only be enabled for network interfaces that require a host-based DCBX client. Configurations on interfaces that implement a hardware DCBX client should leave this check box empty.
@@ -34,7 +34,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>Use auto vlan</term>
+ <term><guilabel>Use auto vlan</guilabel></term>
<listitem>
<para>
This option indicates whether VLAN discovery should be performed. If this box is checked, then the <firstterm>FCoE Initiation Protocol</firstterm> (FIP) VLAN discovery protocol will run on the Ethernet interface once the link configuration has been validated. If they are not already configured, network interfaces for any discovered FCoE VLANs will be automatically created and FCoE instances will be created on the VLAN interfaces. This option is enabled by default.
9 years, 5 months
[install-guide/f21-branch] Typo fix in CustomSpoke_FileSystems and an xref in CustomSpoke
by pbokoc
commit 0807dd5d204f334e75f02b91ab35c58ff3c63f52
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 18:48:47 2014 +0100
Typo fix in CustomSpoke_FileSystems and an xref in CustomSpoke
en-US/CustomSpoke.xml | 5 +++++
en-US/CustomSpoke_FileSystems.xml | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml
index 9cc1a0d..b44aaa5 100644
--- a/en-US/CustomSpoke.xml
+++ b/en-US/CustomSpoke.xml
@@ -34,6 +34,11 @@
<para>
Then, select the newly created mount point in the list on the left side. A set of controls will display on the right side of the screen, allowing you to change its mount point, the device on which it will physically reside, its capacity, file system, etc. When you change any settings, press <guilabel>Update Settings</guilabel> on the bottom right. This will save the adjusted configuration; you can now create another mount point, or select a different existing one and adjust its settings as well.
</para>
+ <note>
+ <para>
+ For a description of available device and file system types, see <xref linkend="sect-installation-gui-manual-partitioning-filesystems" />.
+ </para>
+ </note>
<para>
To remove a mount point, select it in the list and press the <guilabel>-</guilabel> button below.
</para>
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 766d8c5..753eb37 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -20,7 +20,7 @@
</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" />.
</para>
</listitem>
<listitem>
9 years, 5 months
[install-guide] (4 commits) ...Adding text to CustomSpoke
by pbokoc
Summary of changes:
6692714... Moving info about biosboot/efi on gpt/mbr into Recommended (*)
2cf42a3... You can rescan disks in CustomSpoke to have them show up in (*)
22c34cb... Adding Device and File System Types to CustomSpoke (*)
f728cee... Adding text to CustomSpoke (*)
(*) This commit already existed in another branch; no separate mail sent
9 years, 5 months
[install-guide/f21-branch] Adding text to CustomSpoke
by pbokoc
commit f728cee51f53b40e2e62f0dabd836978a0e654f6
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 18:45:43 2014 +0100
Adding text to CustomSpoke
en-US/CustomSpoke.xml | 59 +++++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 57 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml
index a59eb4d..9cc1a0d 100644
--- a/en-US/CustomSpoke.xml
+++ b/en-US/CustomSpoke.xml
@@ -6,9 +6,64 @@
<section id="sect-installation-gui-manual-partitioning">
<title>Manual Partitioning</title>
<para>
- text
+ The <guilabel>Manual Partitioning</guilabel> screen allows you to create a storage configuration for your &PRODUCT; system manually, giving you a greater control over your system's storage.
+ </para>
+ <para>
+ In most other installers for both Linux and other operating systems, disk partitioning usually takes a "bottom-up" approach. In these installers, you first create underlying devices such as LVM physical volumes, then you create a layout such as LVM on top of them, then you create file systems on top of logical volumes, and the last step is usually assigning a mount point to each volume as needed.
+ </para>
+ <para>
+ <application>Anaconda</application> uses an opposite approach. First, you create all separate mount points you need, and everything needed to create them (creating a volume group, logical volumes inside it, and physical volumes where the volume group will reside) is performed automatically. You can then adjust the automatic settings as you require.
+ </para>
+ <note>
+ <para>
+ No permanent changes will be made to your disks during the actual partitioning process. The configuration you have selected will only be written to your system after you press the <guilabel>Begin installation</guilabel> button in <xref linkend="sect-installation-gui-installation-summary" />.
+ </para>
+ </note>
+ <para>
+ <remark>TODO: screen</remark>
+ </para>
+ <para>
+ When you first open the <guilabel>Manual Partitioning</guilabel> screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in <xref linkend="sect-installation-gui-storage-partitioning" />. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear.
+ </para>
+ <para>
+ Here, you can choose a partitioning scheme such as <guilabel>LVM</guilabel> or <guilabel>BTRFS</guilabel> and click the <guilabel>Click here to create them automatically</guilabel> to prompt the installer to create a basic partitioning layout; this layout follows the guidelines described in <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. The created layout is a basic layout where partition/volume sizes are determined automatically based on the total amount of available space.
+ </para>
+ <para>
+ Click the <guilabel>+</guilabel> button to add a mount point. In the dialog window that opens, choose a mount point such as <filename class="directory">/</filename> or <filename class="directory">/home</filename>, and the desired capacity for the mount point (such as <literal>10GB</literal> or <literal>500MB</literal>). Note that specifying the mount point is mandatory, but you do not have to specify the capacity at this point; this is useful when adding a mount point which you want to make larger than the current available space permits. Then, click <guilabel>Add mount point</guilabel> to add it to the list using the default settings, which means it will be created as a logical volume, and a new volume group will be created for it unless one already exists.
+ </para>
+ <para>
+ Then, select the newly created mount point in the list on the left side. A set of controls will display on the right side of the screen, allowing you to change its mount point, the device on which it will physically reside, its capacity, file system, etc. When you change any settings, press <guilabel>Update Settings</guilabel> on the bottom right. This will save the adjusted configuration; you can now create another mount point, or select a different existing one and adjust its settings as well.
+ </para>
+ <para>
+ To remove a mount point, select it in the list and press the <guilabel>-</guilabel> button below.
+ </para>
+ <para>
+ The exact steps for configuring your storage depend on your specific needs and your system configuration. Procedures for creating specific layouts are described further in this chapter. Before you start, you should also review <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> and <xref linkend="sect-installation-gui-manual-partitioning-advice" /> for a list of requirements and tips for partitioning your disks for &PRODUCT;.
+ </para>
+ <para>
+ Below the list of existing mount points two fields, showing you how much free space is left on your storage devices, and how much total space they have.
+ </para>
+ <para>
+ Click the <guilabel><replaceable>X</replaceable> storage devices selected</guilabel> to view a summary of currently selected storage devices; this may help you with orientation in more complicated storage schemas. Devices displayed here are the ones you have selected in <xref linkend="sect-installation-gui-storage-partitioning" />. If you want to add or remove any storage devices from your configuration, return to that screen and change your selection.
+ </para>
+ <para>
+ You can press the <guilabel>Reset All</guilabel> button in the bottom right corner at any time to reset the storage configuration to the state it was in when you last opened the <guilabel>Manual Partitioning</guilabel> screen. This means that if you modify the storage configuration, leave the screen, and then come back, the Reset button will reset the configuration back to the already modified state, discarding only the changes you have made recently, not all changes to the storage configuration since you booted the installer.
+ </para>
+ <para>
+ To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press <guilabel>Rescan Disks</guilabel> and wait until the scanning process completes. Then, press <guilabel>OK</guilabel> to return to <xref linkend="sect-installation-gui-storage-partitioning" />; all detected disks including any new ones will be displayed in the <guilabel>Local Standard Disks</guilabel> section.
+ </para>
+ <para>
+ <remark>TODO: screen</remark>
+ </para>
+ <para>
+ After you finish configuring your system storage, press <guilabel>Done</guilabel> in the top left corner to save the configuration and return to the <guilabel>Installation Summary</guilabel> screen. At this point, the installer will check if your storage configuration is valid. If an error was detected, a message will be displayed at the bottom of the screen. Click the message to open a dialog window explaining what kind of error has been detected (for example, you put <filename class="directory">/boot</filename> on a Btrfs subvolume, or you did not create a BIOS Boot partition when your system requires one).
+ </para>
+ <para>
+ If such a message is displayed, go back and fix any issues found by the installer; otherwise you will not be able to proceed with the installation. You can also press <guilabel>Done</guilabel> again to return to the <guilabel>Installation Summary</guilabel> anyway, but a storage configuration error will prevent you from starting the actual installation process.
+ </para>
+ <para>
+ If no error message is displayed and if you made any changes since the last time you have visited this screen, a summary dialog will appear, displaying a detailed list of the changes you made. Review the list and click <guilabel>Accept Changes</guilabel> to proceed with <xref linkend="sect-installation-gui-installation-summary" />, or click <guilabel>Cancel & Return to Custom Partitioning</guilabel> if you want to make any more changes.
</para>
-
<xi:include href="CustomSpoke_AddPhysical.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="CustomSpoke_SoftwareRAID.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="CustomSpoke_AddLVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
9 years, 5 months
[install-guide/f21-branch] Adding Device and File System Types to CustomSpoke
by pbokoc
commit 22c34cb5b4bbcfde77f8f50ed9b4b4d1d5311ff2
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 18:45:33 2014 +0100
Adding Device and File System Types to CustomSpoke
en-US/CustomSpoke_FileSystems.xml | 79 ++++++++++++++++++++++++++++++++++++-
1 files changed, 78 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 13d2894..766d8c5 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -6,6 +6,83 @@
<section id="sect-installation-gui-manual-partitioning-filesystems">
<title>Device and File System Types</title>
<para>
- text
+ &PRODUCT; supports multiple types of devices and file systems. The two lists below offer a short description of each device and file system 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.
+ </para>
+ <itemizedlist>
+ <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.
+ </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" />.
+ </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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>RAID</guilabel> - Creating two or more software RAID partitions allows you to create a software RAID device. One RAID partition is assigned to each disk on the system. See <xref linkend="sect-installation-gui-manual-partitioning-swraid" /> for instructions on creating software RAID.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>BTRFS</guilabel> - Btrfs is a file system with several device-like features. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. See <xref linkend="sect-installation-gui-manual-partitioning-btrfs" /> for more information about creating Btrfs volumes.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>File Systems</title>
+ <listitem>
+ <para>
+ <guilabel>ext4</guilabel> - The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journaling. Ext4 is the default and recommended file system used by &PRODUCT; The maximum supported size of a single ext4 file system is 50 TB.
+ </para>
+ </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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>ext2</guilabel> - An ext2 file system supports standard Unix file types, including regular files, directories, or symbolic links. It provides the ability to assign long file names, up to 255 characters.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>swap</guilabel> - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. A swap partition should always be created; see <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for details such as the recommended size.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>vfat</guilabel> - The VFAT file system is a Linux file system that is compatible with Microsoft Windows long file names on the FAT file system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>BIOS Boot</guilabel> - A very small partition required for booting from a device with a GUID partition table (GPT) on BIOS systems and UEFI systems in BIOS compatibility mode. See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for details.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>EFI System Partition</guilabel> - A small partition required for booting a device with a GUID partition table (GPT) on a UEFI system. See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for details.
+ </para>
+ </listitem>
+ </itemizedlist>
</section>
9 years, 5 months
[install-guide/f21-branch] You can rescan disks in CustomSpoke to have them show up in StorageSpoke
by pbokoc
commit 2cf42a3c905ac51dc9e4882a9d5654f40d642a6c
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 18:01:26 2014 +0100
You can rescan disks in CustomSpoke to have them show up in StorageSpoke
en-US/StorageSpoke.xml | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/en-US/StorageSpoke.xml b/en-US/StorageSpoke.xml
index d6d8671..125fe72 100644
--- a/en-US/StorageSpoke.xml
+++ b/en-US/StorageSpoke.xml
@@ -20,7 +20,10 @@
<remark>TODO: screen</remark>
</para>
<para>
- In the top part of the screen, all locally available storage devices (SATA, IDE and SCSI hard drives, USB flash drives, etc.) are displayed in the <guilabel>Local Standard Disks</guilabel> section. Local disks are detected when the installer starts - any storage devices connected after the installation has started will not be shown. If you need to additional local storage devices, you must restart the installation.
+ In the top part of the screen, all locally available storage devices (SATA, IDE and SCSI hard drives, USB flash drives, etc.) are displayed in the <guilabel>Local Standard Disks</guilabel> section. Local disks are detected when the installer starts - any storage devices connected after the installation has started will not be shown.
+ </para>
+ <para>
+ If you need to additional local storage devices, select <guilabel>I will configure partitioning</guilabel> and press <guilabel>Done</guilabel> to move to <xref linkend="sect-installation-gui-manual-partitioning" />. Then, connect any new hard drives you want to make available during the installation, and press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press <guilabel>Rescan Disks</guilabel> and wait until the scanning process completes. Then, press <guilabel>OK</guilabel> to return to <xref linkend="sect-installation-gui-storage-partitioning" />; all detected disks including any new ones will be displayed in the <guilabel>Local Standard Disks</guilabel> section.
</para>
<para>
The <guilabel>Specialized & Network Disks</guilabel> section below shows advanced network storage (such as iSCSI and FCoE disks) currently configured. When you first open this screen, no such devices will be displayed because they can not be automatically detected; to search for network storage devices <guilabel>Add a disk</guilabel> button and proceed with <xref linkend="sect-installation-gui-installation-destination" />. Any network storage you configure will then show up in the <guilabel>Specialized & Network Disks</guilabel> the same way local disks are shown above.
9 years, 5 months