Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStephan Mueller
2011-03-04 10:28:02 UTC
Description of problem:
The following kickstart partitioning scheme worked on a 10GB hard disk on RHEL6 (note, this is part of a script and the variables are resolved to: FSTYPE==ext4, VGNAME==VolGroup01, ENC==--encrypt or empty):
logvol / --fstype $FSTYPE --name=root --vgname=$VGNAME --size=2048 --grow $ENC
logvol swap --fstype swap --name=LvSwap --vgname=$VGNAME --size=256 --grow --maxsize=512 $ENC
logvol /var/log --fstype $FSTYPE --name=varlog --vgname=$VGNAME --size=200 --grow --maxsize=2048 --fsoptions="defaults,nodev,noexec,nosuid" $ENC
## Optional partitions, you MAY (de)activate and resize as appropriate
logvol /home --fstype $FSTYPE --name=home --vgname=$VGNAME --size=50 --grow --maxsize=10000 --fsoptions="defaults,nodev" $ENC
logvol /var --fstype $FSTYPE --name=var --vgname=$VGNAME --size=500 --grow --maxsize=50000 $ENC
logvol /var/log/audit --fstype $FSTYPE --name=audit --vgname=$VGNAME --size=2000 $ENC
logvol /tmp --fstype $FSTYPE --name=temp --vgname=$VGNAME --size=1000 $ENC
On the RHEL6.1 alpha ISO, the 10GB partition is insufficient - the /tmp partition cannot be created any more. lvm pvdisplay and lvm vgdisplay show a 10GB partition, but lvdisplay shows:
root: 5GB
swap: 384MB
varlog: 288MB
home: 32MB
var: 768MB
audit: 2GB
You see that root is bigger than it need be.
Version-Release number of selected component (if applicable):
RHEL 6.1 alpha ISO
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0530.html