I've been a happy amanda user for quite some time now but now I've a little 
problem. I backup to disk and backups occassionally stay in holding because 
of a shortage of disk space (I'm using 2.4.3 - want to upgrade soon to 2.4.4 
to be able to use autoflush). This hasn't been a problem as I just ran 
amflush but now I've some dumps that I can't flush. This has happened for a 
while now and I get mails like this:

DUMP SUMMARY:
                                     DUMPER STATS                  TAPER STATS  
HOSTNAME   DISK       L   ORIG-KB    OUT-KB COMP% MMM:SS     KB/s MMM:SS     
KB/s
----------------------- -------------------------------------- ---------------
arda       /            NO FILE TO FLUSH 
arda       /boot        NO FILE TO FLUSH 
bree       /            NO FILE TO FLUSH 
bree       /boot        NO FILE TO FLUSH 
dale       /            NO FILE TO FLUSH 
dale       /boot        NO FILE TO FLUSH 


I get this "NO FILE TO FLUSH" message for every disk in my disklist, and there 
are dumps for those disks in the holding disk.

In the last couple of days amdump doesn't seem to complete properly. Although 
ps shows me no relevant processes, I have to run amcleanup - then I get the 
above mail. I get the message about the unprocessed logfile and when I look 
at the logfile I see:

DISK amflush arda /
DISK amflush arda /boot
DISK amflush bree /
DISK amflush bree /boot
DISK amflush dale /
DISK amflush dale /boot
START amflush date 20030601
START driver date 20030601
STATS driver startup time 0.015
START taper datestamp 20030601 label TIZdaily45 tape 0
INFO taper tape TIZdaily45 kb 0 fm 0 [OK]
FINISH driver date 20030601 time 1.116

This is the entire logfile, except that I have removed a number of  the
"DISK amflush" lines to shorten this mail.

Can anyone suggest what's going on here, and how I might flush these 
outstanding dumps ?



Niall