Boost log uses all inodes if file system is full

[Michi Henning]

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://svn.boost.org/trac/boost/ticket/11016

We need to track this.

[Michi Henning (michihenning)]

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).

[Pat McGowan (pat-mcgowan)]

I say yes to cherry picking a fix

[Michi Henning (michihenning)]

Pat, can you help here? I can prepare a diff against the boost 1.55 source once the maintainer has finalised the fix. But I don't know what to do to get the patched boost log into the archives.

[Michi Henning (michihenning)]

The linked branch implements a work-around for the bug in boost log. This means we won't need a patched boost log lib.

Also, I don't think system image is affected because the RTM release does not use boost log. (We added that functionality later.)

Pat, I think this means that Canonical System Image is not affected. If you agree could you remove it from the bug?

[Pat McGowan (pat-mcgowan)]

good to know, can track it here for vivid as well