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

Bug#838919: marked as done (debian-installer: please calculate swap parition according to max RAM supported by the motherboard)

Your message dated Mon, 26 Sep 2016 17:27:23 +0100
with message-id <1474907243.2829.18.camel@decadent.org.uk>
and subject line Re: Bug#838919: debian-installer: please calculate swap parition according to max RAM supported by the motherboard
has caused the Debian Bug report #838919,
regarding debian-installer: please calculate swap parition according to max RAM supported by the motherboard
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
immediately.)


-- 
838919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838919
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Severity: wishlist

As far as I can tell, d-i calculates the size of the swap partition according to the curently installed amount of RAM.

Whenever the RAM is upgraded later on, the swap parition no longer fulfills its intended purpose, in cases when it would be needed to store hibernate images, since the parition was calculated to store a much smaller RAM image.

A more desirable method would be for d-i to use 'dmidecode' to probe the system's memory controller for the maximum amount of RAM that is supported and to calculate the swap partition size according to that.

-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (1111, 'stable'), (1001, 'oldstable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Mon, 2016-09-26 at 10:23 -0400, Lennart Sorensen wrote:
> On Mon, Sep 26, 2016 at 05:06:18PM +0300, Martin-Éric Racine wrote:
> > 
> > Package: debian-installer
> > Severity: wishlist
> > 
> > As far as I can tell, d-i calculates the size of the swap partition
> > according to the curently installed amount of RAM.
> > 
> > Whenever the RAM is upgraded later on, the swap parition no longer
> > fulfills its intended purpose, in cases when it would be needed to
> > store hibernate images, since the parition was calculated to store
> > a much smaller RAM image.
> > 
> > A more desirable method would be for d-i to use 'dmidecode' to
> > probe the system's memory controller for the maximum amount of RAM
> > that is supported and to calculate the swap partition size
> > according to that.
> 
> Of course many people never upgrade their ram, and often going beyond 50%
> of maximum gets very expensive.
> 
> Also many people never suspend.
> 
> Also dmidecode is x86 only and some older systems didn't have it, so it
> wouldn't help the majority of architectures.
> 
> So while it is an idea, I am not convinced it doesn't actually create
> problems.

Right, this proposal sounds like it would be worse than the current
heuristic in general.

A better way to deal with this is to use LVM and leave some space
unallocated initially so it's possible to grow swap or whatever other
partition needs it later.

Closing as we're not likely to make this change.

Ben.

> Besides I could move the disk to a new system later which could have
> even more ram, so even making it as large as dmidecode says won't solve
> all cases.  I would think that case is at least as likely as maxing out
> the ram in a machine is.
> 
-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: