Bug 98137 - Max Swap Size
Summary: Max Swap Size
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: rhl-ig-as-x86
Version: 2.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Sandra Moore
QA Contact: Tammy Fox
URL: http://www.redhat.com/docs/manuals/en...
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-26 21:34 UTC by Need Real Name
Modified: 2014-08-04 22:23 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2003-07-02 16:12:03 UTC


Attachments (Terms of Use)

Description Need Real Name 2003-06-26 21:34:05 UTC
Description of problem:

http://www.redhat.com/docs/manuals/enterprise/RHEL-AS-2.1-Manual/install-
guide/s1-diskpartitioning.html

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 
partition. 

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:

Always

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


Expected results:


Additional info:

Comment 1 Sandra Moore 2003-07-02 16:12:03 UTC
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.