Tesla Ye Nash

Scenario :  I've created a VM with a RHEL7 guest.  The partition layout is a standard, primary partition for /boot and LVM for the rest--namely, /usr , /var, /home, swap and / (rootfs).  After installing updates and some other packages, the /usr directory began to fill up. In order to mitigate the situation, I created an additional primary partition with an XFS filesystem, as that is the preferred/default FS in RHEL7.     # parted /dev/vda mkpart P3 xfs 14G 16G The above command instructs "parted" to operate on the /dev/vda disk and create primary partition 3 with XFS filesystem starting at 14G and ending at 16G.   Next, I added the physical partition to LVM with the following command:        # pvcreate /dev/vda   Then, extend the volume group with the physical partition with:      # vgextend rhel /dev/vda3   and      # lvextend -L+2G /dev/rhel/usr Finally, to grow the filesystem I executed      # xfs_growfs /dev/rhel/usr     

The default storage setup in a new Red Hat Enterprise Linux 7 installation is an LVM partitioning scheme with an XFS boot partition outside of the LVM scheme, and the root and home partitions comprising the main volume group on an XFS filesystem. This is a departure from the previous default filesystem type ext4 . Some important behavioral and administrative differences between the ext4 filesystem and the xfs filesystem are addressed in the RedHat Documentation, chapter 6 in the “Storage Administration Guide” specifically. The key items addressed pertain to Filesystem repair , Metadata error behavior , Quotas , Filesystem resize and Inode numbers among other things. One nice feature of the XFS filesystem is the native backup and restoration feature with the xfsdump and xfsrestore utilities, respectively. The xfsdump utility supports incremental backups to tape drives or regular file images. The incremental backups are possible due to the use of different dump levels .