here is my amcleanup :
bash-2.05b$ amcleanup daily
amcleanup: no unprocessed logfile to clean up

I also did a grep amflush inside the amanda log dir without any result :(

Frederic Medery
System Administrator

LexUM, University of Montreal



Frank Smith wrote:

--On Thursday, October 14, 2004 15:16:31 -0400 Frederic Medery <dist-list AT 
LEXUM.UMontreal DOT CA> wrote:

I can confirm that all my dumps are inside the directory

OK, perhaps amflush thinks amdump is still running. Try running 'amcleanup config', if it says it did anything then

some previous amdump didn't exit cleanly. If it says there's
nothing to process then that wasn't the problem and you'll
need to keep looking.
  Is anything written to Amanda's log directory (or system
logs, for that matter) when you run amflush?

Frank

Frederic Medery
System Administrator

LexUM, University of Montreal



Frank Smith wrote:

--On Thursday, October 14, 2004 13:12:22 -0400 Frederic Medery <dist-list AT 
LEXUM.UMontreal DOT CA> wrote:

Here is my amflush command :
Scanning /amanda/daily...
20040823: found Amanda directory.
20040910: found Amanda directory.
20041012: found Amanda directory.

Multiple Amanda directories, please pick one by letter:
A. 20040823
B. 20040910
C. 20041012
Select directories to flush [A..C]: [ALL]


As you can see I saw the dump I can flush, The prob occure with each dump

Just because the directory is there doesn't mean anything is in it.  What
does an 'ls -lR' of one of those directories show?  Sometimes Amanda doesn't
properly clean up the holdingdisk. The directory only gets removed if its
completely empty and sometimes there are 0 byte chunks left behind if a
client backup fails.  Amflush isn't too smart and just looks for the dated
directories to ask you about but then doesn't have anything to actually
write to tape if you pick one.

Frank

Frederic Medery
System Administrator

LexUM, University of Montreal



Frank Smith wrote:

--On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <dist-list AT 
LEXUM.UMontreal DOT CA> wrote:

Hello,
every time I do a amflush i received this report :

The dumps were flushed to tape daily-05.
The next tape Amanda expects to use is: daily-02.


STATISTICS:
                       Total       Full      Daily
                     --------   --------   --------
Estimate Time (hrs:min)    0:00
Run Time (hrs:min)         0:01
Dump Time (hrs:min)        0:00       0:00       0:00
Output Size (meg)           0.0        0.0        0.0
Original Size (meg)         0.0        0.0        0.0
Avg Compressed Size (%)     --         --         -- Filesystems Dumped         
   0          0          0

Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min) 0:00 0:00 0:00

Tape Size (meg)             0.0        0.0        0.0
Tape Used (%)               0.0        0.0        0.0
Filesystems Taped             0          0          0

Avg Tp Write Rate (k/s) -- -- -- USAGE BY TAPE:

Label          Time      Size      %    Nb
daily-05       0:00       0.0    0.0     0


How can i troubleshoot amflush (I run it as amanda user)

First make sure there is something to flush.  Are there actually
files in your holdingdisk or are you running it because of a
report that says 'warning, some files may be left on holdingdisk'?
The warning just means there is a possibilty of something to flush,
not that there definately is.
Also, make sure that whatever is in your holdingdisk belongs to
the config you're trying to amflush.
I would guess there's something in your debug directory as well
(I think /tmp/amanda is the default), but I've never had occasion to
look there after an amflush.

Related question for others on the group:  why does amanda mark a
tape as being used even when nothing is written to it?  Shouldn't
the update to the tapelist be done only after something was written?

Frank

thanks

--
Frederic Medery
System Administrator

LexUM, University of Montreal