touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1421060

Title:
  Boost log uses all inodes if file system is full

Status in the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  New

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

  We need to track this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421060/+subscriptions