Bug 98137 - Max Swap Size
Max Swap Size
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: rhl-ig-as-x86 (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Sandra Moore
Tammy Fox
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-06-26 17:34 EDT by Need Real Name
Modified: 2014-08-04 18:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-02 12:12:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2003-06-26 17:34:05 EDT
Description of problem:


With reference to the above URL, a customer suggests that the section 
entitled "Recommended Partitioning Scheme" should be clearer and state that the 
max size for a Swap partition is 2GB. Please also mention that if the user 
requires more than 2GB for Swap partition, they should create more than 1 swap 

This is because this customer have 4 GB of RAM and as recommended by this 
section, their swap partition should be at least equal to the amount of RAM on 
their system which is 4GB but they failed to create a swap partition bigger 
than 2GB and wonder what they should do. They couldn't find the information in 
this manual on how to solve this by creating an additional swap partition.

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

rhl-ig-as-x86(EN)-2.1-HTML-RHI (2002-03-22T11:09-0400)

How reproducible:


Steps to Reproduce:
1. Please refer to the manual.
Actual results:

Expected results:

Additional info:
Comment 1 Sandra Moore 2003-07-02 12:12:03 EDT
Great suggestion, thanks for submitting it. I've added this information to the
swap partition recommendations. The new information will be available in the
next release of the Installation Guide.

Thanks again!

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