Bug 471148

Summary: problem with partitioning, swap space doesn't grow over 1G
Product: Red Hat Enterprise Linux 5 Reporter: Michael Hideo <mhideo>
Component: doc-Installation_GuideAssignee: Ruediger Landmann <rlandman+disabled>
Status: CLOSED CURRENTRELEASE QA Contact: Content Services Development <ecs-dev-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: ddomingo, rlerch
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When using swap --grow in a kickstart file without setting --maxsize parameter at the same time, anaconda imposes a restriction on the maximum size of the swap partition. It does not allow it to grow to fill the device. The maximum size is given by the formula provided in section 4.18.4 of the RHEL5 Installation Guide - "Recommended Partitioning Scheme". The swap guidelines provided in the kickstart documentation are incorrect. For systems with less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-16 03:57:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 462734    
Bug Blocks:    

Comment 1 Michael Hideo 2008-11-12 00:48:15 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
When using swap --grow in a kickstart file
without setting --maxsize parameter at the same time, anaconda imposes a restriction on the maximum size of the swap partition.  It does not allow it to grow to fill the device.  The maximum size is given by the formula provided in section 4.18.4 of the RHEL5 Installation Guide - "Recommended Partitioning Scheme".  The swap guidelines provided in the kickstart documentation are incorrect.

For systems with less than 2GB of physical memory, the imposed limit is twice the amount of physical memory.  For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.

Comment 2 Don Domingo 2008-11-14 00:28:56 UTC
revised (in source) --grow definition in "Kickstart Options" of RHEL5.3 Installation Guide:

<quote>
--grow — Tells the partition to grow to fill available space (if any), or up to the maximum size setting.

Note
 If you use --grow= without setting --maxsize= on a swap partition, Anaconda will limit the maximum size of the  partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.
</quote>