Is there any work in progress to detect a low disk space condition for disk based media? Currently when I run out of space I end up with Bacula using up tiny bits and pieces all over the place which mucks up my 'one volume = one job' assumption and requires a bit of cleaning up pain.
Three ways I can think of solving this: 1. a "don't span volumes" option in the job resource 2. a "maximum volumes per job" option in the job resource 3. a way to get the storage daemon to hold the job if disk space is less than some amount, eg "minimum space = 5GB" #1 would work nicely in my case. #2 is just a more general version of #1. In this case the job would just fail if the media became full, a message would be sent to me, and I'd fix the problem and rerun whatever jobs were necessary. #3 would send a message and then just cause the sd to hang and stop accepting further data to that device until the disk space increased again. I could fix the problem and the job would continue again. Thanks James ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
