[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#346589: marked as done (partman-auto: creates too large swap partitions)

Your message dated Mon, 1 Nov 2010 18:59:07 +0100
with message-id <20101101175907.GL3395@mykerinos.kheops.frmug.org>
and subject line Closing bug already fixed (kinda)
has caused the Debian Bug report #346589,
regarding partman-auto: creates too large swap partitions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

346589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346589
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: partman-auto
Version: 41
Severity: normal

This report applies to the sarge version, but apparently this is still 
the case in the unstable version.

When creating the swap partition, partman-auto chooses twice the total 
memory size. On a modern computer, this is incredibly huge. For a 
server, this can be of some use, but on a desktop computer this is a 
waste of space and an annoyance. On a desktop, the only thing that can 
really make use of such a large swap space is an application becoming 
mad and hugging all memory - in which case you don't want a too large 

Please limit the swap size for the desktop scheme. A value like 256 MB 
sounds reasonable.

 .''`.           Josselin Mouette        /\./\
: :' :           josselin.mouette@ens-lyon.org
`. `'                        joss@debian.org
  `-  Debian GNU/Linux -- The power of freedom

--- End Message ---
--- Begin Message ---
Version: 93

In theis version of partman-auto, we decided to limit the size of the
swap partition to 200% of physical RAM (needed for suspend to disk).

That fixes this bug, to my understanding.


Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: