I've set amanda's holding space to be ``all of the disk, but leave XXX
free''

(
holdingdisk hd1 {
    comment "main holding disk"
    directory "/whopper/amanda/lto"     # where the holding disk is
    use -10 Gb          # how much space can we use on it
                        # a non-positive value means:
                        #        use all space but that value
}

It looks like amanda treats this as:

Upon startup, check how much free diskspace is there, subtract 10G from
that, and use that as the disksize.

My amanda dumps take all night (well over 12 hours) and the disks are
active, meaning that the amount of free diskspace is fluctuating.

However amanda does *NOT* adapt her idea of how much disksapce is
available.
She simply calculates at startup how much she can use, and uses that number
for the rest of the night.

Ideally amanda should look every time a chunk is written to disk how much
space ios free, but at least she should check at the start of each new
dump/tar how much diskspace is free.
% amstatus lto
Using /volume/amanda/share/amanda/lto/amdump from Thu May  3 18:00:01 MET
DST 2001

[snipped]
james:/whopper/data/autotest             033409192k wait for dumping
[snipped]
james:/whopper/newhome2                  038438112k writing to tape (7:59:55)   

All the other dumps are finished.

SUMMARY          part     real estimated
                          size      size
partition       :  27
estimated       :  27          125219454k
failed          :   1            2860734k           (  2.28%)
wait for dumping:   1           33409192k           ( 26.68%)
dumping to tape :   0                  0k           (  0.00%)
dumping         :   0        0k        0k (  0.00%) (  0.00%)
dumped          :  25 85863904k 88949528k ( 96.53%) ( 68.57%)
wait for writing:   0        0k        0k (  0.00%) (  0.00%)
writing to tape :   1 38438112k 38678328k ( 99.38%) ( 30.70%)
failed to tape  :   0        0k        0k (  0.00%) (  0.00%)
taped           :  24 47425792k 50271200k ( 94.34%) ( 37.87%)
6 dumpers idle  : no-diskspace
taper writing, tapeq: 0
network free kps:   126880
holding space   :  4672463k ( 10.84%)
 dumper0 busy   : 12:37:57  ( 96.85%)
 dumper1 busy   :  7:37:54  ( 58.51%)
 dumper2 busy   :  8:24:40  ( 64.49%)
 dumper3 busy   :  9:06:01  ( 69.77%)
   taper busy   :  2:39:11  ( 20.34%)
 0 dumpers busy :  0:23:56  (  3.06%)        no-diskspace:  0:23:56 (100.00%)
 1 dumper busy  :  3:31:44  ( 27.06%)        no-diskspace:  3:31:13  ( 99.76%)
                                               start-wait:  0:00:31  ( 0.24%)
 2 dumpers busy :  0:41:29  (  5.30%)        no-diskspace:  0:41:00  ( 98.86%)
                                               start-wait:  0:00:28  ( 1.14%)
 3 dumpers busy :  0:47:51  (  6.11%)        no-diskspace:  0:47:16  ( 98.79%)
                                               start-wait:  0:00:34  ( 1.21%)
 4 dumpers busy :  7:37:35  ( 58.47%)        no-diskspace:  7:32:38  ( 98.92%)
                                               start-wait:  0:04:56  ( 1.08%)
james:/home/netscradd/Mail # df -k /whopper
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/md/dsk/d99      433727332 391286116 38103943    92%    /whopper

Note that holding space sais it has only 4 G free
Whereas the df shows that the holding disk should have approx 28G free




Kind regards,
 --
Gerhard den Hollander                           Phone +31-10.280.1515
Technical Support Jason Geosystems BV           Fax   +31-10.280.1511
                                   (When calling please note: we are in GMT+1)
[EMAIL PROTECTED]                          POBox 1573
visit us at http://www.jasongeo.com                 3000 BN Rotterdam  
JASON.......#1 in Reservoir Characterization        The Netherlands

      This e-mail and any attachment is/are intended solely for the named
  addressee(s) and may contain information that is confidential and privileged.
       If you are not the intended recipient, we request that you do not
         disseminate, forward, distribute or copy this e-mail message.
      If you have received this e-mail message in error, please notify us
           immediately by telephone and destroy the original message.

Reply via email to