Manual Partitioning
     __________________________________________________________

   The Manual Partitioning screen allows you to create a storage
   configuration for your Fedora system manually, giving you a
   greater control over your system's storage.

   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.

   Anaconda 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.

Note

   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 Begin installation button in Installation Summary.

   When you first open the Manual Partitioning screen, the column
   on the left side will display all previously existing
   partitions on all drives which you selected as installation
   targers in Installation Destination. If none of the selected
   drives contain any existing partitions, then a message
   informing you that no mount points currently exist will appear.

   Here, you can choose a partitioning scheme such as LVM or BTRFS
   and click the Click here to create them automatically to prompt
   the installer to create a basic partitioning layout; this
   layout follows the guidelines described in Recommended
   Partitioning Scheme. The created layout is a basic layout where
   partition/volume sizes are determined automatically based on
   the total amount of available space.

   Click the + button to add a mount point. In the dialog window
   that opens, choose a mount point such as / or /home, and the
   desired capacity for the mount point (such as 10GB or 500MB).
   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 Add mount
   point 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.

   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 Update Settings 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.

Note

   For a description of available device and file system types,
   see Device, File System and RAID Types.

   To remove a mount point, select it in the list and press the -
   button below.

   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 Recommended
   Partitioning Scheme and Advice on Partitions for a list of
   requirements and tips for partitioning your disks for Fedora.

   Below the list of existing mount points are two fields, showing
   you how much free space is left on your storage devices and how
   much total space they have.

   Click the X storage devices selected 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 Installation
   Destination. If you want to add or remove any storage devices
   from your configuration, return to that screen and change your
   selection.

   You can press the Reset All 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 Manual Partitioning 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.

   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 Rescan Disks and wait until the
   scanning process completes. Then, press OK to return to
   Installation Destination; all detected disks including any new
   ones will be displayed in the Local Standard Disks section.

   After you finish configuring your system storage, press Done in
   the top left corner to save the configuration and return to the
   Installation Summary 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
   /boot on a Btrfs subvolume, or you did not create a BIOS Boot
   partition when your system requires one).

   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 Done again to
   return to the Installation Summary anyway, but a storage
   configuration error will prevent you from starting the actual
   installation process.

   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 Accept Changes to proceed
   with Installation Summary, or click Cancel & Return to Custom
   Partitioning if you want to make any more changes.

Creating Standard Partitions

   Standard partitions are the most common type of partition, with
   the widest support across operating systems. For example,
   Microsoft Windows uses exclusively physical partitions and can
   not natively work with LVM or Btrfs. Most Fedora partitioning
   setups will also require at least one standard partition for
   the /boot directory, and possibly also another standard
   partition with the BIOS Boot or EFI System file system to store
   the boot loader.

   See the full Fedora Installation Guide, available at
   http://docs.fedoraproject.org/ for additional information about
   the concepts behind physical partitions.

   Follow the procedure below to create mount points on standard
   physical partitions:

   Procedure 1. Creating Standard Partitions
    1. Click the + button at the bottom of the list showing
       existing mount points. A new dialog window will open.
    2. In the new dialog window, specify a mount point for which
       you want to create a separate mount point - for example, /.
       Optionally, specify a size for the partition using standard
       units such as MB or GB (for example, 50GB). Then, click Add
       mount point to add the mount point and return to the main
       partitioning screen.

Note
       When creating a swap partition, specify the mount point as
       swap. For a BIOS Boot partition, use biosboot. For an EFI
       System Partition, use /boot/efi.
       For information about these partition types, see
       Recommended Partitioning Scheme.
    3. The mount point has now been created using the default
       settings, which means it has been created as an LVM logical
       volume. Select the newly created mount point in the left
       pane to configure it further, and convert it to a physical
       partition by changing the Device Type option to Standard
       Partition. Then, click Update Settings in the bottom right
       corner of the screen.
    4. In the Device(s) section on the right side of the screen,
       you can see that the partition has been assigned to one or
       more hard drives. Click the Modify button to configure on
       which drive this partition will be created.
    5. In the Configure Mount Point dialog, you can specify which
       physical devices (disks) this volume may reside on. You can
       select one or more disks which will be used to hold this
       volume by holding down Ctrl and clicking each disk in the
       list. If you select multiple disks here, Anaconda will
       determine where exactly the partition should be created
       based on how you configured the rest of the installation.
       If you want to make sure that this partition is placed on a
       specific hard drive, select only that drive and unselect
       all others.
       After you finish configuring the partition's location,
       click Save to return to the main Manual Partitioning
       screen.
    6. Configure other settings specific to the partition - its
       Mount Point, Desired Capacity, and File System. Press
       Update Settings to apply any changes to the configuration.

   Repeat this procedure for any additional standard partitions
   you want to create.

Creating Software RAID

   Redundant arrays of independent disks (RAIDs) are constructed
   from multiple storage devices that are arranged to provide
   increased performance and, in some configurations, greater
   fault tolerance. See Device, File System and RAID Types a
   description of different kinds of RAIDs.

   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.

Important

   This section only explains how to create software RAID with
   standard (physical) partitions. However, you can also configure
   LVM volume groups and Btrfs volumes to use RAID and place their
   logical volumes or Btrfs subvolumes on top of this RAID array.
   See Creating a Logical Volume Managament (LVM) Layout and
   Creating a Btrfs Layout for instructions on creating RAID in
   LVM and Btrfs.

Note

   RAID configuration options are only visible if you have
   selected two or more disks for installation. At least two disks
   are required to create a RAID device, and some RAID layouts
   will require more. Requirements for different types of RAID are
   described in Device, File System and RAID Types.

   Follow the procedure below to create software RAID:

   Procedure 2. Creating Software RAID
    1. Click the + button at the bottom of the list showing
       existing mount points. A new dialog window will open.
    2. In the new dialog window, specify a mount point for which
       you want to create a separate software RAID partition - for
       example, /. Optionally, specify a size for the new
       partition using standard units such as MB or GB (for
       example, 50GB). Then, click Add mount point to add the
       mount point and return to the main partitioning screen.

Note
       When creating a mount point for swap on software RAID,
       specify the mount point as swap.
    3. The mount point has now been created using the default
       settings, which means it has been created as an LVM logical
       volume. Select the newly created mount point in the left
       pane to configure it further, and convert it to a software
       RAID partition by changing the Device Type option to RAID.
    4. Choose a RAID type from the RAID Level drop-down menu.
       Available RAID types and their requirements are described
       in Device, File System and RAID Types.
    5. In the Device(s) section on the right side of the screen,
       you can see that the partition has been assigned to several
       physical disks. Click the Modify button to configure on
       which drives this partition will be created.
    6. In the Configure Mount Point dialog, you can specify which
       physical devices (disks) this partition may reside on. You
       can select one or more disks which will be used to hold
       this partition by holding down Ctrl and clicking each disk
       in the list. If you want to make sure that this partition
       is placed on a specific set of hard drives, select only
       those drives and unselect all others.
       After you finish configuring the partition's location,
       click Save to return to the main Manual Partitioning
       screen.
    7. Configure other settings specific to the partition - its
       Mount Point, Desired Capacity, and File System. Press
       Update Settings to apply any changes to the configuration.

   Repeat this procedure for any additional standard partitions
   with software RAID you want to create.

Creating a Logical Volume Managament (LVM) Layout

   Logical Volume Management (LVM) presents a simple logical view
   of underlying physical storage space, such as hard drives or
   LUNs. Partitions on physical storage are represented as
   physical volumes that can be grouped together into volume
   groups. Each volume group can be divided into multiple logical
   volumes, each of which is analogous to a standard disk
   partition. Therefore, LVM logical volumes function as
   partitions which can span multiple physical disks.

   See the full Fedora Installation Guide, available at
   http://docs.fedoraproject.org/ for additional information about
   the concepts behind Logical Volume Management.

Warning

   Some partition types - notably the /boot directory and the BIOS
   Boot and EFI partitions - can not be placed on logical volumes.
   Use standard physical volumes for them. See Recommended
   Partitioning Scheme for more information.

   Follow the procedure below to create LVM logical volumes and
   volume groups.

   Procedure 3. Creating LVM Logical Volumes and Groups
    1. Click the + button at the bottom of the list showing
       existing mount points. A new dialog window will open.
    2. In the new dialog window, specify a mount point for which
       you want to create a separate logical volume - for example,
       /. Optionally, specify a size for the volume using standard
       units such as MB or GB (for example, 50GB). Then, click Add
       mount point to add the volume and return to the main
       partitioning screen.

Note
       When creating a mount point for swap on LVM, specify the
       mount point as swap.
    3. 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 Device Type option to LVM Thin
       Provisioning.
    4. In the Volume Group menu, you can see that the volume has
       been assigned to an automatically created volume group,
       which is named after the Fedora variant you are installing
       (for example, fedora-server. Click the Modify button under
       the drop-down menu to access the volume group settings.
    5. In the Configure Volume Group dialog, you can change the
       volume group's name, its RAID level (see Device, File
       System and RAID Types for information about available RAID
       types), 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 Ctrl and clicking each disk in the
       list.

Note
       If you select a redundant RAID type (such as RAID1
       (Redundancy)), 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.
       You can also make sure that the volume group is encrypted
       by selecting the Encrypt option; this will enable LUKS
       encryption for the entire volume group. See the Fedora
       Security Guide, available at
       http://docs.fedoraproject.org/, for information about LUKS
       disk encryption.
       Additionally, you can set a fixed size for the volume group
       by selecting the Fixed option from the Size policy menu and
       entering a size for the volume group.
       After you finish configuring the volume group settings,
       click Save to return to the main Manual Partitioning
       screen.

Note
       The configuration dialog does not allow you to specify the
       size of the volume group's physical extents. 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 vgcreate command, or use a Kickstart file with
       the volgroup --pesize=size command.
    6. If you need to create more than one volume group, open the
       Volume Group drop-down menu and select the Create a new
       volume group 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 Save.
       The new volume group will then become available in the
       Volume Group drop-down menu; you can then go through your
       existing mount points and change this setting to assign
       them to a different volume group.
    7. Configure other settings specific to the logical volume -
       its Mount Point, Desired Capacity, File System, and Name.
       Press Update Settings to apply any changes to the
       configuration.

   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.

   For each mount point you create, review its settings and make
   sure that it is assigned to the correct group, that it has
   sufficient capacity, and that it has a descriptive name so you
   can identify the volume later if you need to.

Creating a Btrfs Layout

   Btrfs is a type of file system, but it has several features
   characteristic of a storage device. It is designed to make the
   file system tolerant of errors, and to facilitate the detection
   and repair of errors when they occur. It uses checksums to
   ensure the validity of data and metadata, and maintains
   snapshots of the file system that can be used for backup or
   repair.

   Creating a Btrfs layout is somewhat similar to LVM (described
   in Creating a Logical Volume Managament (LVM) Layout) with
   slightly different terminology. A Btrfs volume is the
   equivalent of an LVM volume group, and a Btrfs subvolume is
   similar to a LVM logical volume. An important difference to
   note is how Anaconda reports sizes for separate mount points:
   For LVM, the exact size of each logical volume is shown next to
   each mount point in the left pane, while with Btrfs, the total
   size of the entire volume is shown next to each subvolume.

Warning

   Some partition types - notably the /boot and /usr directories
   and the BIOS Boot and EFI partitions - can not be placed on
   Btrfs subvolumes. Use standard physical volumes for them (or an
   LVM logical volume for /usr). See Recommended Partitioning
   Scheme for more information.

   Follow the procedure below to create Btrfs volumes and
   subvolumes:

   Procedure 4. Creating Btrfs Subvolumes and Volumes
    1. Click the + button at the bottom of the list showing
       existing mount points. A new dialog window will open.
    2. In the new dialog window, specify a mount point for which
       you want to create a separate logical volume - for example,
       /. Optionally, specify a size for the volume using standard
       units such as MB or GB (for example, 50GB). Then, click Add
       mount point to add the volume and return to the main
       partitioning screen.

Note
       When creating a mount point for swap on Btrfs, specify the
       mount point as swap.
    3. The mount point has now been created using the default
       settings, which means it has been created as an LVM logical
       volume. Select the newly created mount point in the left
       pane to configure it further, and convert it to a Btrfs
       subvolume by changing the Device Type option to Btrfs.
       Then, click Update Settings in the bottom right corner of
       the screen.
    4. In the Volume menu, you can see that the subvolume has been
       assigned to an automatically created volume, which is named
       after the Fedora variant you are installing (for example,
       fedora-server00. Click the Modify button under the
       drop-down menu to access the volume settings.
    5. In the Configure Volume dialog, you can change the volume's
       name, its RAID level (see Device, File System and RAID
       Types for information about available RAID types), and you
       can also specify which physical devices (disks) this volume
       should reside on. You can select one or more disks which
       will be used to hold this volume by holding down Ctrl and
       clicking each disk in the list.

Note
       If you select a redundant RAID type (such as RAID1
       (Redundancy)), the volume will take up twice its actual
       size on your disks. A 5 GB volume with RAID1 will take up
       10 GB of space.
       You can also make sure that the volume is encrypted by
       selecting the Encrypt option; this will enable LUKS
       encryption for the entire volume. See the Fedora Security
       Guide, available at http://docs.fedoraproject.org/, for
       information about LUKS disk encryption.
       Additionally, you can set a fixed size for the volume by
       selecting the Fixed option from the Size policy menu and
       entering a size for the volume group.
       After you finish configuring the Btrfs volume settings,
       click Save to return to the main Manual Partitioning
       screen.
    6. If you need to create more than one Btrfs volume, open the
       Volume drop-down menu and select the Create a new volume
       group 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 volume, and click Save. The new
       volume will then become available in the Volume Group
       drop-down menu; you can then go through your existing mount
       points and change this setting to assign them to a
       different volume.
    7. Configure other settings specific to the subvolume - its
       Mount Point, Desired Capacity, File System, and Name. Press
       Update Settings to apply any changes to the configuration.

   Repeat this procedure for any additional Btrfs subvolumes you
   want to create. Note that when creating additional subvolumes,
   a new volume is not automatically created each time; instead,
   any additional subvolumes are assigned to an existing volume.

   For each mount point you create, review its settings and make
   sure that it is assigned to the correct volume, that it has
   sufficient capacity, and that it has a descriptive name so you
   can identify the subvolume later if you need to.

Device, File System and RAID Types

   Fedora 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.

   To select a device type or a file system of a partition or a
   logical volume, select it in the list in Manual Partitioning
   and select a Device Type and a File System from their
   respective drop-down menus on the right side of the screen.
   Then, click Update Settings and repeat this process for all
   mount points you want to modify.

   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 Software RAID as the device type to create software RAID
   with standard partitions. For detailed instructions, see
   Creating a Btrfs Layout, Creating a Logical Volume Managament
   (LVM) Layout, and Creating Software RAID as needed.

   Device Types
     * Standard Partition - A standard partition can contain a
       file system or swap space. Standard partitions are most
       commonly used for /boot and the BIOS Boot and EFI System
       partitions. LVM logical volumes or Btrfs subvolumes are
       recommended for most other uses. See the full Fedora
       Installation Guide, available at
       http://docs.fedoraproject.org/ for additional information
       about the concepts behind physical partitions.
     * LVM - Choosing LVM as the Device Type 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 Creating a Logical Volume Managament
       (LVM) Layout. Also see the full Fedora Installation Guide,
       available at http://docs.fedoraproject.org/ for some
       additional information about LVM in general.
     * LVM Thin Provisioning - Using thin provisioning, you can
       manage a storage pool of free space, known as a thin pool,
       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.
     * RAID - 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 Creating Software
       RAID for instructions on creating software RAID.
     * BTRFS - 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 Creating a Btrfs Layout
       for more information about creating Btrfs volumes.

   File Systems
     * ext4 - 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 Fedora
       Workstation and Cloud. The maximum supported size of a
       single ext4 file system is 50 TB.
     * ext3 - 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 fsck utility
       every time a crash occurs.
     * ext2 - 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.
     * swap - 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
       Recommended Partitioning Scheme for details such as the
       recommended size.
     * xfs - 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. Starting with Fedora 22, XFS is the
       default and recommended file system on Fedora Server.

Important
       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.
     * vfat - The VFAT file system is a Linux file system that is
       compatible with Microsoft Windows long file names on the
       FAT file system.
     * BIOS Boot - 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
       Recommended Partitioning Scheme for details.
     * EFI System Partition - A small partition required for
       booting a device with a GUID partition table (GPT) on a
       UEFI system. See Recommended Partitioning Scheme for
       details.

   Software RAID Types
     * RAID0 (Performance) - 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.
     * RAID1 (Redundancy) - 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.
     * RAID4 (Error Checking) - 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.
     * RAID5 (Distributed Error Checking) - 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.
     * RAID6 (Redundant Error Checking) - 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.
     * RAID10 (Performance, Redundancy) - 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.

Recommended Partitioning Scheme

   In most cases, at least the following mount points should
   always be created:

   /boot - 500 MB
          This partition contains the operating system kernel,
          which allows Fedora 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 /boot partition is adequate.

Important

          If your system has a hardware RAID controller, be aware
          that some BIOS types do not support booting from it. In
          that case, the /boot partition must be created on a
          partition outside of the RAID array, such as on a
          separate hard drive.

          Also note that the /boot directory can not be placed on
          a LVM logical volume or a Btrfs subvolume. Use a
          standard partition.

   / (root) - 10 GB
          This is where the root directory is located. The root
          directory is the top level of the directory structure.
          By default, all files are written to this partition
          unless a different partition is mounted in the path
          being written to (for example, /boot or /home). If you
          follow the recommended scheme described in this section,
          this will be the partition where most software packages
          will be installed.

          For a minimal installation, a 5 GB root partition will
          be sufficient. However, for most common installations
          which include extra packages and a graphical user
          interface, the root partition should be at least 10 GB;
          with 20 GB being sufficient for most common use cases.

Note

          The / mount point is the top of the Linux Filesystem
          Hierarchy, and is referred to as the root file system,
          or root. The /root directory, sometimes pronounced
          "slash-root", is the home directory for the root user.

   /home - at least 10 GB
          To store user data separately from system data, create a
          dedicated mount point 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 Fedora
          without erasing user data files. During the
          installation, a separate /home partition will be created
          if there are 50 GB or more free space for your Fedora
          installation.

          When using Fedora as a workstation for normal use with a
          graphical environment, this mount point should have the
          most disk space assigned to it, as it will likely hold
          the most data (user settings, images, videos, etc).

   swap - based on your system parameters
          Swap partitions support virtual memory; data is written
          to them when there is not enough RAM to store the data
          your system is processing. This partition's size is a
          function of system memory workload, not total system
          memory, and therefore is not equal to the total system
          memory size. Therefore, it is important to analyze what
          applications a system will be running and the load those
          applications will serve in order to determine the system
          memory workload. Application providers and developers
          should be able to provide some guidance.

          When the system runs out of swap space, the kernel
          terminates processes as the system RAM memory is
          exhausted. Configuring too much swap space results in
          storage devices being allocated but idle and is a poor
          use of resources. Too much swap space can also hide
          memory leaks. The maximum size for a swap partition and
          other additional information can be found in the
          mkswap(8) man page.

          The table below provides the recommended size of a swap
          partition depending on the amount of RAM in your system
          and whether you want sufficient memory for your system
          to hibernate. If you let the installation program
          partition your system automatically, the swap partition
          size will be established using these guidelines.
          Automatic partitioning setup assumes hibernation is not
          in use, and the maximum size of the swap partition is
          limited to 10% of the total size of the hard drive. If
          you want to set up enough swap space to allow for
          hibernation, or if you want to set the swap partition
          size to more than 10% of the system's storage space, you
          must edit the partitioning layout manually.

          Table 1. Recommended System Swap Space

   Amount of RAM in the system Recommended swap space Recommended
   swap space if allowing for hibernation
   less than 2 GB 2 times the amount of RAM 3 times the amount of
   RAM
   2 GB - 8 GB Equal to the amount of RAM 2 times the amount of
   RAM
   8 GB - 64 GB 0.5 times the amount of RAM 1.5 times the amount
   of RAM
   more than 64 GB workload dependent hibernation not recommended

          At the border between each range listed above (for
          example, a system with 2 GB, 8 GB, or 64 GB of system
          RAM), discretion can be exercised with regard to chosen
          swap space and hibernation support. If your system
          resources allow for it, increasing the swap space may
          lead to better performance.

          Distributing swap space over multiple storage devices -
          particularly on systems with fast drives, controllers
          and interfaces - also improves swap space performance.

   BIOS Boot (1 MB) or EFI System Partition (200 MB)
          The GRUB2 boot loader can be installed either in the
          Master Boot Record (MBR) or the GUID Partition Table
          (GPT) of the boot device. In order to determine which of
          these methods to use, the installation program considers
          the following variations:

        Systems with BIOS firmware and UEFI systems in BIOS
                compatibility mode
                If the disk is already formatted, the partitioning
                scheme is retained. If the disk is not formatted,
                or you have erased all existing partitions from
                the disk, the installer will choose the following:

               o MBR if the size of the disk is less than 2 TB
                 (terabytes)
               o GPT if the size of the disk is more than 2 TB

Note

                You can force the installer to use GPT on disks
                smaller than 2 TB by using the inst.gpt boot
                option as described in the full Fedora
                Installation Guide, available at
                http://docs.fedoraproject.org/. However, the
                opposite is not possible - you can not use MBR on
                disks larger than 2 TB.

                You need to create a BIOS Boot partition with a
                size of 1 MB to install on a system with BIOS
                firmware if the disk containing the boot loader
                uses GPT. If the disk uses a MBR, no special
                partition is necessary on a BIOS system.

        Systems with UEFI firmware
                Only GPT is allowed on UEFI systems. In order to
                install on a formatted disk with a MBR, it must be
                reformated and relabeled. All data currently on
                the disk will be lost.

                UEFI-based systems require an EFI System Partition
                at least 50 MB in size (recommended size is 200
                MB), regardless of the partitioning scheme.

Important

          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.

          Also note that if your system does not require any of
          these partitions, they will not be shown in the File
          System menu in mount point options.

   Many systems have more partitions than the minimum listed
   above. Choose partitions based on your particular needs. See
   Advice on Partitions for additional information and advice.

Note

   Only assign storage capacity to those partitions you require
   immediately. You may allocate free space at any time, to meet
   needs as they occur.

   If you are not sure how best to configure the partitions for
   your computer, accept the automatic default partition layout
   provided by the installation program as described in
   Installation Destination.

Advice on Partitions

   There is no best way to partition every system; the optimal
   setup depends on how you plan to use the system being
   installed. However, the following tips may help you find the
   optimal layout for your needs:
     * Consider encrypting any partitions and volumes which might
       contain sensitive data. Encryption prevents unauthorized
       people from accessing the data on the partitions, even if
       they have access to the physical storage device. In most
       cases, you should at least encrypt the /home partition,
       which contains user data.
     * In some cases, creating separate mount points for
       directories other than /, /boot and /home may be useful;
       for example, on a server running a MySQL database, having a
       separate mount point for /var/lib/mysql will allow you to
       preserve the database during a reinstallation without
       having to restore it from backup afterwards. However,
       having unnecessary separate mount points will make storage
       administration more difficult.
     * Some special restrictions apply to certain directories with
       regards on which partitioning layouts can they be placed.
       Notably, the /boot directory must always be on a physical
       partition (not on an LVM volume or a Btrfs subvolume), and
       /usr can not be on a Btrfs subvolume.
     * If you are new to Linux, consider reviewing the Linux
       Filesystem Hierarchy Standard at
       http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html
       for information about various system directories and their
       contents.
     * Each kernel installed on your system requires approximately
       20 MB on the /boot partition. The default partition size of
       500 MB for /boot should suffice for most common uses;
       increase the size of this partition if you plan to keep
       many kernels installed at the same time.
     * The /var directory holds content for a number of
       applications, including the Apache web server, and is used
       by the DNF package manager to temporarily store downloaded
       package updates. Make sure that the partition or volume
       containing /var has at least 3 GB.
     * The contents of the /var directory usually change very
       often. This may cause problems with older solid state
       drives (SSDs), as they can handle a lower number of
       read/write cycles before becoming unusable. If your system
       root is on an SSD, consider creating a separate mount point
       for /var on a classic (platter) HDD.
     * The /usr directory holds the majority of software on a
       typical Fedora installation. The partition or volume
       containing this directory should therefore be at least 5 GB
       for minimal installations, and at least 10 GB for
       installations with a graphical environment.
     * If /usr or /var is partitioned separately from the rest of
       the root volume, the boot process becomes much more complex
       because these directories contain boot-critical components.
       In some situations, such as when these directories are
       placed on an iSCSI drive or an FCoE location, the system
       may either be unable to boot, or it may hang with a Device
       is busy error when powering off or rebooting.
       This limitation only applies to /usr or /var, not to
       directories below them. For example, a separate partition
       for /var/www will work without issues.
     * Consider leaving a portion of the space in an LVM volume
       group unallocated. This unallocated space gives you
       flexibility if your space requirements change but you do
       not wish to remove data from other volumes. You can also
       select the Thin provisioning device type for the partition
       to have the unused space handled automatically by the
       volume.
     * The size of an XFS file system can not be reduced - if you
       need to make a partition or volume with this file system
       smaller, you must back up your data, destroy the file
       system, and create a new, smaller one in its place.
       Therefore, if you expect needing to manipulate your
       partitioning layout later, you should use the ext4 file
       system instead.
     * Use Logical Volume Management (LVM) if you anticipate
       expanding your storage by adding more hard drives after the
       installation. With LVM, you can create physical volumes on
       the new drives, and then assign them to any volume group
       and logical volume as you see fit - for example, you can
       easily expand your system's /home (or any other directory
       residing on a logical volume).
     * Creating a BIOS Boot partition or an EFI System Partition
       may be necessary, depending on your system's firmware, boot
       drive size, and boot drive disk label. See Recommended
       Partitioning Scheme for information about these partitions.
       Note that the graphical installer will not let you create a
       BIOS Boot or EFI System Partition if your system does not
       require one - in that case, they will be hidden from the
       menu.
     * If you need to make any changes to your storage
       configuration after the installation, Fedora repositories
       offer several different tools which can help you do this.
       If you prefer a command line tool, try
       system-storage-manager.
