Jon,

On Mon, Jun 26, 2006 at 11:01:51AM -0400, Jon LaBadie wrote:
> On Mon, Jun 26, 2006 at 10:39:26AM -0400, Brian Cuttler wrote:
> > First, Solaris 9 with Amanda 2.4.4
> > 
> > I have changed the "reserve" parameter from commented out (prior to
> > the friday night run) to 30, and this morning, lowered it to 10. This
> > I had thought was the cuprit.
> > 
> > > grep reserve amanda.conf
> > reserve 10 # percent
> > 
> > holdingdisk hd1 {
> >     comment "main holding disk"
> >     directory "/amanda/work"    # where the holding disk is
> >     use 70 Gb           # how much space can we use on it
> >                         # a non-positive value means:
> >                         #        use all space but that value
> >     chunksize 1Gb       # size of chunk if you want big dump to be
> >                         # dumped on multiple files on holding disks
> >                         #  N Kb/Mb/Gb split images in chunks of size N
> >                         #             The maximum value should be
> >                         #             (MAX_FILE_SIZE - 1Mb)
> >                         #  0          same as INT_MAX bytes
> >     }
> > 
> > I do not believe holdingdisk is set to no in the dumptype.
> 
> amadmin has a command, I think disklist, which can be used to
> print out many of the dump parameters for a single (or multiple)
> DLE's.  This would be after the parsing of amanda.conf and all
> the included dumptypes.  I'm pretty sure "holding disk yes/no"
> is among those printed.

Yes, in fact all entries in the disklist have holdingdisk yes set.

> amadmin ninfo disklist | more
line 4:
    host csserv:
        interface default
    disk /:
        program "DUMP"
        priority 0
        dumpcycle 7
        maxdumps 4
        maxpromoteday 10000
        strategy STANDARD
        compress NONE
        auth BSD
        kencrypt NO
        holdingdisk YES
        record YES
        index NO
        skip-incr NO
        skip-full NO

line 5:
    host csserv:
        interface default


> amadmin ninfo disklist | grep holdingdisk
        holdingdisk YES
        holdingdisk YES
        holdingdisk YES
        holdingdisk YES
        holdingdisk YES
        holdingdisk YES
(many lines removed)


> I don't recall, is your DLE small enough to fit the available
> holding disk space.  Not your 70 GB, but actual available
> space (df <holding disk> cmd or 70GB (which ever is smaller)
> minus whatever is stored under <holding disk> finally multiplied
> by percent unreserved.

Few of the DLE at level 0 should be forced direct to tape, certainly
none of the non-level-0 DLE.

# df -kh /amanda/work
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c7t6d0s0       67G   118M    66G     1%    /amanda

With a reserve value of 10, we should be ablet o utilize 60 Gig
of work area, or do I have some value set backwards ?


> amcheck is seeing your holding disks, right?

Yes it is.

> amcheck -s ninfo
Amanda Tape Server Host Check
-----------------------------
WARNING: holding disk /amanda/work: only 69728377 KB free (73400320 KB requested

> Maybe someone can tell us the actual lines in log or debugging
> files that would say why amanda selects direct to tape.

                                                thank you,

                                                Brian


---
   Brian R Cuttler                 brian.cuttler AT wadsworth DOT org
   Computer Systems Support        (v) 518 486-1697
   Wadsworth Center                (f) 518 473-6384
   NYS Department of Health        Help Desk 518 473-0773