Bug 182080 - 2GB as swap partition's size limit for FC4 i386/x86_64?
Summary: 2GB as swap partition's size limit for FC4 i386/x86_64?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-20 08:46 UTC by Robinson Tiemuqinke
Modified: 2015-01-04 22:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-27 05:17:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robinson Tiemuqinke 2006-02-20 08:46:18 UTC
Description of problem:
What's the size limit for a swap partition for FC4? Is the 2GB limit useful 
size per swap partition still in effect or not? from mkswap manual it says 
that the limit is lift off. But really need to confirm that for i386 arch.

And for x86_64 arch, what's the maximum useful size per swap area?

The following is cut from mkswap manual:

The maximum useful size of a swap area depends on the architecture and kernel  
version.   It  is  roughly 2GiB  on  i386,  PPC,  m68k, ARM, 1GiB on sparc, 
512MiB on mips, 128GiB on alpha and 3TiB on sparc64. For kernels after 2.3.3 
there is no that limitation.


Version-Release number of selected component (if applicable):
util-linux-2.12p-9.13
kernel-2.6.13-1.1532_FC4
kernel-2.6.15-1.1831_FC4


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Karel Zak 2006-02-20 14:27:20 UTC
It's more than 2GB for i386 and x86_64. I think the real limit is max size of
block device (probably 32bit - 16Tb, 64bit - 8Exabyte).

Reassingning to kernel team -- maybe they know more exact numbers.

Comment 2 Dave Jones 2006-02-27 05:17:30 UTC
iirc, you can have up to 32 64GB swaps active at the same time.
Posting such questions to linux-kernel is a better bet for such queries.
Bugzilla is for tracking bugs.


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