atop floods /run partition
Bug #1530167 reported by
Alexey Lebedeff
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Michael Polenchuk | ||
7.0.x |
Won't Fix
|
High
|
Michael Polenchuk | ||
8.0.x |
Fix Released
|
High
|
Michael Polenchuk |
Bug Description
I'm running Mirantis OpenStack 7.0 in virtualbox using launch_8gb.sh script.
After few days /run partition became 100% full, and controller node became unfunctional due to this.
The root cause is atop that actively writes data to /run/atop/atop.acct - bad idea, given that /run is on tmpfs.
There is an unfixed upstream bug about this issue - https:/
Changed in fuel: | |
milestone: | none → 7.0-updates |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-linux |
tags: |
added: area-library removed: area-linux |
tags: | added: team-bugfix |
no longer affects: | fuel/mitaka |
tags: | added: on-verification |
tags: | added: on-verification |
tags: | removed: on-verification |
To post a comment you must log in.
It looks a common problem.
atop uses /var/run/atop.acct (by default) to record accounting data about processes. Depending on system behaviour it may grow relatievely slow, or quite fast [1] (see screenshot [2]).
Although there is an opinion that accounting file should be rewritten daily I don't think it's a good idea, since in that case you loose some data that might be needed for debugging.
Anyway, the problem doesn't seems related to atop itself, but to the way it was started.
Reassigning to fuel-library team to let them fix puppet manifests.
[1] https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 650222 /bugs.debian. org/cgi- bin/bugreport. cgi?att= 1;bug=650222; msg=26; filename= 650222- screenshot. png
[2] https:/