Description of problem: In the normal flow, users are expected to use auto partitioning when installing RHVH 4.0. However, if a user decides to do custom partitioning, then a few requirements need to be met: 1. LVM thin provisioning needs to be used 2. / needs to reside on a thin LV 3. /var needs to be a separate mount point (can be an LV or anything else)
(In reply to Fabian Deutsch from comment #0) > Description of problem: > In the normal flow, users are expected to use auto partitioning when > installing RHVH 4.0. > > However, if a user decides to do custom partitioning, then a few > requirements need to be met: > > 1. LVM thin provisioning needs to be used > 2. / needs to reside on a thin LV So that it will be possible to extend it? > 3. /var needs to be a separate mount point (can be an LV or anything else)
>> 2. / needs to reside on a thin LV > So that it will be possible to extend it? The primary reason why / is on a thin LV is, that we only need to allocate as many space in the LV's thinpool as really is used by the file-system. This is over-provisioning. We can do this, because we do not except the root file-system to grow much, however, because customers could install additional rpms we do need to have the ability to allocate more space to the file-system if more space is required (i.e. when additional rpms are installed). I.e. currently the root file-system of Node is 6GB in size, but we currently only require 1.3GB. At the end however, yes, you could also resize the file-system
A previous email about custom partitioning also included: * / must be at least 6GB * xfs or ext4 must be used Do these requirements still apply, too?
Yes
Now published at https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/installation-guide/#Advanced_RHVH_Install