> I don't know what you have been told before.
>
> As you wrote
>
> R>> I still have close to 4 to 5 backup
> R>> dumps created by amanda in my holding space [which failed across
various
> R>> weeks].
>
> I have to assume that amdump is not working, either.

Backups which run in the night seems to be running fine. For example
yesterday's night backup ran well before spitting out Input/Output tape
errors [I'm assuming its a bad tape problem - I'm planning to replace such
tapes]

> How many amanda-processes are running already?

amanda   23560 97.5  0.0  2124   20 ?        R    15:51  72:30 ./amflush
DailySet1
amanda   23561  0.0  0.0  2132    4 ?        S    15:51   0:00 driver
DailySet1 nodump
amanda   23562  0.0  0.0  2784    4 ?        S    15:51   0:00 taper
DailySet1
amanda   23563  0.0  0.0  2808    4 ?        S    15:51   0:00 taper
DailySet1
root     26989  0.0  0.2  3576  644 pts/4    S    17:05   0:00 grep amanda

> Try to kill all the amdump/amflush-processes, they seem to lock each
> other. Run amcleanup afterwards, then amcheck.

I do this: 1) Kill all the processes which belong to amanda 2) Run amcleanup
3) Run amflush again, but it slowly eats away CPU and amflush gets stuck.

> After that amflush should run fine.

Well, in my case, it doesn't :)