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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421060 Title: Boost log uses all inodes if file system is full To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421060/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
