Alex,
Holding disk on "wcnotes" is 36 gig (in a single partition) the
level 1 backup that went direct to tape last night was 11 gig
(5 gig from another partion, same system).
This is why I thought it wasn't a spool space issue. In this
case we should have had sufficient room as the 4 partitons
involved contributed 11 gig, 5 gig, 1 gig and .7 gig. Even with
all in spool at one time I would not expect to see this behaviour.
Not that I'm don't want to upgrade Amanda, but you know how it is.
Without the excuse its hard to pull the time from another project
to fix something that is working (and amanda is very reliable).
Besides, I don't like mystery behaviour.
This just doesn't look like a spool capacity issue ?
thanks,
Brian
> On Apr 10, 2001, [EMAIL PROTECTED] (Brian Cuttler) wrote:
>
> > Wondering if this isn't a "feature" of 2.2.6 and a must upgrade
> > for performance issue at our site.
>
> > The smaller problem partition is only 4 gig, the larger in excess
> > of 18, both partitions continue to grow.
>
> I'm afraid you'll have to upgrade. In 2.4.1 or so, we have introduced
> `chunksize', that lets Amanda back up large disks regardless of the
> maximum holding disk file size.
>
> --
> 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
