Boost log uses all inodes if file system is full
Bug #1421060 reported by
Michi Henning
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
unity-scopes-api (Ubuntu) |
Fix Released
|
High
|
Michi Henning |
Bug Description
boost::log, if file rotation happens while the file system is full, creates hundreds of empty log files per log directory, eventually consuming all available inodes.
But reported here: https:/
We need to track this.
Related branches
lp://staging/~michihenning/unity-scopes-api/fix-inode-leak
- PS Jenkins bot (community): Approve (continuous-integration)
- Paweł Stołowski (community): Approve
-
Diff: 118 lines (+26/-26)1 file modifiedsrc/scopes/internal/Logger.cpp (+26/-26)
Changed in unity-scopes-api (Ubuntu): | |
importance: | Undecided → High |
affects: | unity-scopes-api (Ubuntu) → canonical-devices-system-image |
Changed in unity-scopes-api (Ubuntu): | |
importance: | Undecided → High |
Changed in unity-scopes-api (Ubuntu): | |
assignee: | nobody → Michi Henning (michihenning) |
status: | New → In Progress |
Changed in unity-scopes-api (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in unity-scopes-api (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The boost log maintainer has published a fix that partially fixes the problem. Instead of losing thousands of inodes, we now only lose dozens. But, even once a complete fix is done, it won't become available to us until boost 1.58.
Is it worth cherry-picking the eventual fix and shipping our own patched version of libboost_log?
Note that the problem appears only once /home is full. But, once full, we are losing inodes very rapidly (potentially many thousands per minute while scopes are active).