On Fri, Sep 03, 2010 at 01:19:50PM -0500, Dustin J. Mitchell wrote: > On Fri, Sep 3, 2010 at 11:13 AM, Valeriu Mutu <[email protected]> wrote: > > Next time 'amdump' runs, it will not be able to use the size of holding > > disk specified and the warning will be printed: > > NOTES: > > ??driver: WARNING: /data3/amanda/holdingdisk/Daily1/: 880803840 KB > > requested, but only 2351104 KB available. > > > > Does this mean that Amanda will use a holding disk of 2351104Kb? Or will it > > flush the entire holding disk area to tape (880803840Kb) once the 2351104Kb > > are used? Also, after the flush, will it use 880803840Kb of holding disk > > space or just 2351104Kb? > > Yes, Amanda will use whatever space it finds available. if autoflush > is enabled, it will begin by flushing any existing dumps to tape, > after which it will use the full available space. > > If autoflush is enabled, it would seem sensible to consider any > existing holding files to be available space when deciding whether to > print this warning, but this isn't currently done (that I can see, > anyway).
Isn't a decision made before each DLE is dumped whether there is enough holding disk for it? In that case, does the reported amount (i.e. 2.3GB above) serve as an upper limit for the entire amdump run? If so, maybe that part of the code needs to be tweaked to allow use of any space freed by flushed dumps. jl -- Jon H. LaBadie [email protected] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
