[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bacula-devel] Feature request: "minimum spool size" setting

Item: Add a "minimum spool size" setting, defining a minimum level of free 
space to spool new jobs

Date: 20 March 2008

Origin: Frank Sweetser <fs@xxxxxxx>

What: Add a new SD directive, "minimum spool size" (or similar).  This 
directive would specify a minimum level of free space available for spooling.
If the unused spool space is less than this level, any new spooling requests 
would be blocked as if the "maximum spool size" threshold had bee reached. 
Already spooling jobs would be unaffected by this directive.

Why: I've been bitten by this scenario a couple of times:

Assume a maximum spool size of 100M.  Two concurrent jobs, A and B, are both 
running.  Due to timing quirks and previously running jobs, job A has used 
99.9M of space in the spool directory.  While A is busy despooling to disk, B 
is happily using the remaining 0.1M of spool space.  This ends up in a 
spool/despool sequence every 0.1M of data.  In addition to fragmenting the 
data on the volume far more than was necessary, in larger data sets (ie, tens 
or hundreds of gigabytes) it can easily produce multi-megabyte report emails!

Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
     GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Bacula-devel mailing list

This mailing list archive is a service of Copilotco.