Re: [Boost-bugs] [Boost C++ Libraries] #11016: Boost file logging misbehaves when file system is full

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11016: Boost file logging misbehaves when file system is full
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-02-24 09:06:00

#11016: Boost file logging misbehaves when file system is full
-------------------------------+---------------------
  Reporter:  michi@…           |      Owner:  andysem
      Type:  Bugs              |     Status:  closed
 Milestone:  To Be Determined  |  Component:  log
   Version:  Boost 1.55.0      |   Severity:  Problem
Resolution:  fixed             |   Keywords:
-------------------------------+---------------------

Comment (by andysem):

 Replying to [comment:28 Michi Henning <michi.henning@…>]:
 >
 > Andy, the point is that the threshold isn't reached while the file
 system is full. Therefore, while the "file system full" condition
 persists, a potentially unbounded number of inodes is used up, making a
 bad situation worse.

 If you only set the max_size limit then yes, the files will keep piling
 up. The proper fix for that is to set min_free_space - I assume you don't
 want the empty files to appear in the first place, do you?

 > I'll have a look at min_free_space, thanks for the tip! But, as far as I
 can see, it would have to be at least as large max_size to have any
 effect?

 No, these limits are not related.

 > Is it really that hard to check whether a write failed and, if so, stat
 the file and unlink it if empty? It seems like a simple fix, and it would
 get rid of the empty files. We'd have a more robust system that way.

 The question is not about hard. It's about consistency. A special behavior
 should be backed by a good reason.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/11016#comment:29>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.