On 01/27/2016 03:39 PM, Jean-Louis Martineau wrote: > man amanda.conf: > largestfit > The largest dump image that will fit on the current tape. > > The full dump is too large to fit on the tape, so amanda flush a smaller > dump (the incrementals). > > You found a bug, amanda must always flush dump in datestamp order!!
I don't know if I would be exactly that strict about it, if a run can write multiple tapes, I can see a little bit of shuffling dumps around to fit the tapes better. It seems like basically solving a knapsack problem (at least when hardware compression is off and amanda knows the exact sizes of the dumps and the tapes). I just think amanda should probably not end a taper run while some dumps are on tape but dumps *they depend on* are not. That seems like a sufficient condition to avoid unpleasant surprises. -Chap
