From eaa9cd312ba90f26ace4963fec11ebbd9e51afce Mon Sep 17 00:00:00 2001 From: Petr Bokoc Date: Sep 07 2015 13:02:43 +0000 Subject: Add info about /var and /usr into Partitioning Advice --- diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml index 599cab0..2204e76 100644 --- a/en-US/CustomSpoke_PartitioningAdvice.xml +++ b/en-US/CustomSpoke_PartitioningAdvice.xml @@ -11,7 +11,7 @@ - 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. + 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. @@ -31,7 +31,7 @@ - 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. + 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. @@ -50,13 +50,21 @@ + + 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. + 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. + 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.