On Apr 30, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
>> 1) When I run an amflush I notice that the dump are put on tape starting
>> with the smallest and working its way up to the largest last. Why is
>> this?
> I suspect the theory is to get as many images safely out to tape as
> quickly as possible.
My theory has to do with releasing holding disk space: since a small
image will be flushed more quickly than a large one, we flush the
small one first, and can release its disk space as soon as it
completes. Of course, in the long run (i.e., after everything is
flushed), you end up releasing the same amount of disk space, but, on
average over time, you get more free space flushing the small images
first.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
