Bug 1153817 - I'm apparently using 819 TB / 1 GB of memory
Summary: I'm apparently using 819 TB / 1 GB of memory
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: procps-ng
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 21:05 UTC by Lubomir Rintel
Modified: 2016-07-19 12:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 12:13:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
top (89.65 KB, image/png)
2014-10-16 21:05 UTC, Lubomir Rintel
no flags Details

Description Lubomir Rintel 2014-10-16 21:05:41 UTC
Created attachment 947746 [details]
top

In a libvirt managed LXC domain.

See attached screenshot.

Comment 1 Jaromír Cápík 2014-10-20 18:11:18 UTC
Ahoj Lubomire.

This might be a kernel problem as the new release supports MemAvailable and follows the latest changes in the kernel memory management. I'd like to see what 'free' reports and what you get after switching the 'top' tool to the old default for memory stats (press the 'm' key twice).

Please, let me know.

Thanks,
Jaromir.

Comment 2 Jaromír Cápík 2014-10-20 18:44:15 UTC
Btw. that number represents a percentage, not GBs.

Comment 3 Lubomir Rintel 2015-04-20 17:26:16 UTC
Sorry for a very late reply. The problem seems to be in the way top interprets what's in meminfo -- probably not accounting for MemAvailable being > MemTotal or something like that:

# cat /proc/meminfo
MemTotal:        1048576 kB
MemFree:         1047096 kB
MemAvailable:   12455716 kB

This is in a LXC container, with a cgroup that limits usable memory:

# cat /sys/fs/cgroup/memory/memory.limit_in_bytes
1073741824

Comment 4 Fedora End Of Life 2015-11-04 12:35:53 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-12-02 04:20:35 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Fedora End Of Life 2016-07-19 12:13:56 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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