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

Bug#1081888: marked as done ([RFD] Update partman-auto/cap-ram default value to re-allow hibernation)

Your message dated Fri, 22 Nov 2024 14:45:03 +0100
with message-id <20241122144503.13ebb8792a755569a5c716f0@mailbox.org>
and subject line Re: #1081888 [RFD] Update partman-auto/cap-ram default value to re-allow hibernation
has caused the Debian Bug report #1081888,
regarding [RFD] Update partman-auto/cap-ram default value to re-allow hibernation
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.)


-- 
1081888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081888
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: partman-auto
Version: 167
Tags: d-i

Dear maintainers,
The debconf setting partman-auto/cap-ram was introduced to deal with the very special case of systems with more RAM than disk space with previous recipes setting the minimum (and maximum in most cases) swap size to 100% of RAM size. On the other hand, the maximum swap size of 1GB caused by its default value breaks hibernation in many cases.
partman-auto 167 provides updated recipes with new limits. Swap maximum size is now the lower of 100% of RAM size or ~5% or disk space. This should be enough to deal with the above special case while allowing hibernation on systems with enough disk space.
But partman-auto/cap-ram still gets in the way. I believe it is time to update its default value: either disable it completely, or raise it to a value which does not prevent hibernation on the majority or systems, e.g. 64GB. I hope a consensus can be reached.
--- End Message ---
--- Begin Message --- 
Version: 168

This was fixed shortly.

Closing this bug.

-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---
Reply to: