Feature #10540

Smarter check for free memory in the Upgrader's wrapper

Added by intrigeri 2015-11-12 04:45:32 . Updated 2015-11-12 07:27:42 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2015-11-12
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Upgrader
Deliverable for:
269

Description

Quoting anonym (Bug #8263#note-1):

In our Live system context, where a lot of stuff is in tmpfs:es, looking at the values of free or /proc/meminfo alone isn’t accurate for determining how much memory “really” is free, since the tmpfs usage is included in the buffers. Hence, MemFree is the lower (and safe) bound of how much “really” free memory we have, and MemFree + Buffers + Cache is the upper (and unsafe) bound. The true value should be (at least closer to) MemFree + Buffers + Cache - (sum of usage by tmpfs:es). We should check once against that value instead.


Subtasks


Related issues

Related to Tails - Bug #8263: Deal with memory requirements check in tails-upgrade-frontend-wrapper vs Jessie Resolved 2014-11-14

History

#1 Updated by intrigeri 2015-11-12 04:46:11

  • related to Bug #8263: Deal with memory requirements check in tails-upgrade-frontend-wrapper vs Jessie added

#2 Updated by intrigeri 2015-11-12 06:47:07

> sum of usage by tmpfs:es

This is it (in the same unit as /proc/meminfo by default, i.e. kB):

/bin/df --type=tmpfs --local --output=used --total | tail -n1

#3 Updated by intrigeri 2015-11-12 07:26:18

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:b8a97e4fe5cfcf265b66eb0ebda724ce24bff122.

#4 Updated by intrigeri 2015-11-12 07:27:42

  • Target version set to Tails_2.0
  • % Done changed from 100 to 0
  • Deliverable for set to 269

#5 Updated by intrigeri 2015-11-12 07:27:54

  • blocks #8668 added