On 04/08/10 03:16, Rex Chan wrote:
>  
>> Honestly, the truth is that free space monitoring isn't Bacula's job.
>> Bacula doesn't know what else it's sharing disk space with.
>>
>> That said, the subject has come up before; there has been discussion
>> of how best to handle the problem.  Nothing has been implemented yet
>> though.  As best I recall, the general conclusion of the discussion
>> was that there needed to be some kind of minimum free space directive
>> for disk pools, such that Bacula would decline to create any new
>> volumes if there was less than [directive value] free space on the
>> device.  I'm not sure whether this has actively gone anywhere yet.
> 
> As a workaround, can a run before job script be responsible for
> detecting the condition and then terminating the job? 

That certainly ought to work.  A properly written script, passed the
client name and level, should even be able to make an informed guess at
roughly how much disk the job should require.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users