Bug 7209 - 2nd Swap parition
2nd Swap parition
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
sparc Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-21 14:04 EST by Jeff Shao
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-22 12:27:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Shao 1999-11-21 14:04:32 EST
I created 2 swap partition during install.

I noticed that the system is only configured with one swap area.

I have no entry in /etc/fstab on the 2nd swap

I also have to mkswap on /dev/sdaX

then run swapon to enable it.

thanks
Comment 1 Jay Turner 1999-11-22 12:58:59 EST
Is there any reason that you are creating multiple swap partitions?  With the
introduction of the 2.2.x series of kernels, swap partitions up to 2G are
supported without any trouble.

I will forward this problem with the creation of multiple swap partitions to a
developer for further action.
Comment 2 Jeff Shao 1999-11-22 16:12:59 EST
I have two HDs, and low memory on the Sparc classic, it make more sense to have
two swap area, one per hd so it will use both drive instead all hitting one
single drive.
Comment 3 Christian Hechelmann 1999-11-26 06:35:59 EST
It certainly makes sense to specify more than one swap partition.

1. Total Size of swap area (I know 2.2.x lifted the 128MB barrier)
2. Load balancing. When you add N swap areas (possibly on different disks
   which are connected to different buses) with the same priority you
   get a RAID-0 (striping) like behaviour (-> increased bandwith) as the
   kernel uses these areas in parallel.
Comment 4 Jay Turner 2000-02-22 12:27:59 EST
This issue is resolved in the latest installer (available in beta)

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