Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157310 - ks.cfg "part swap ---recommended" has 2GB limit
Summary: ks.cfg "part swap ---recommended" has 2GB limit
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-10 15:01 UTC by Theo Miller
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-10 19:31:28 UTC


Attachments (Terms of Use)

Description Theo Miller 2005-05-10 15:01:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)

Description of problem:
Ananconda has a 2GB swap partition limit when using the "part swap -recommended" option in a ks.cfg kickstart file

Version-Release number of selected component (if applicable):
anaconda for rhel3

How reproducible:
Always

Steps to Reproduce:
1. Create a kickstart file with the line "part swap --recommended"
2. Kickstart the system
3. Maximum swap partition size will be 2GB, even if it should be more
  

Actual Results:  Swap partition was 2GB on a systems with 4GB and 8GB physical ram in them

Expected Results:  Swap partition should have been two time the physical ram size

Additional info:

Comment 1 Jeremy Katz 2005-05-10 19:31:28 UTC
This is intentional.  Growing the swap partition beyond 2 GB in the general case
ends up leading to less of a performance improvement than you might otherwise
expect.


Note You need to log in before you can comment on or make changes to this bug.