On Thu, 15 May 2003 at 2:49pm, Eric Siegerman wrote

>   - a separate config variable for a "second-chance" taper
>     algorithm (horrible name; suggestions most welcome).  The
>     choices would (to start with) be the same as the ones for the
>     main taper_algo, but they would all be weaker versions that
>     didn't take remaining tape into account -- just like the
>     implicit "weak FIRST" that's used now in the "if" statement
> 
>     Intended usage:
>       taper_algo              LARGESTFIT
>       second_taper_algo       SMALLEST
> 
>     One could emulate the current behaviour like this:
>       taper_algo              <whatever>
>       second_taper_algo       FIRST

I like this idea.  It gives the user more control, which is always a good 
thing.  I, too, have a config that can waste several hours taping stuff it 
knows won't fit.

>   - new options for second-taper-algo (not really useful for the
>     main one):
>       - NEWTAPE -- in other words, if there isn't currently a DLE
>       that will fit, change tapes rather than trying to dump a
>       too-large DLE
> 
>       - SLOP n MB -- i.e. accept a DLE that exceeds the estimated
>       remaining tape by up to the specified amount.  Using this
>       as the main taper_algo seems equivalent to increasing the
>       tape length in the tapetype entry, but in the second-chance
>       position, it lets you say, in effect:
>           I think there are 2 GB left, so look for a DLE that's
>           smaller than that ... Darn, there aren't any; ok,
>           let's gamble, and hope there's really room for 2.2
>           GB.
> 

All very good suggestions.

> P.S.: "DLE" is a new acronym since the last time I used Amanda in
> 1998.  I believe I've been able to infer what it means, but what
> does it *stand for*?

DiskList Entry.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University