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.
