I've run into this situation a couple of times. Amanda doesn't finish running. Top shows it not
being active, though many processes exist if I look by user amandabackup. `df -k` shows the holding
disks completely full with no free space. The tape drive is unloaded and idle. When I run `amstatus
daily`, I see a DLE indicating PARTIAL (i.e. it ran off the end of the tape), I see a few "waiting
for writing to tape", and I see a couple "waiting for holding disk space." So, in other words,
nothing can be done. If I didn't look, it would sit there forever, apparently.
So, to clean it up, I do `amcleanup -k daily`. Then, since I have a significant amount of dumps on
holding disk and can fill most of a tape, I go ahead and run `amflush daily`. I don't want to put
that on automatic, because sometimes there can be tape difficulties, and I would end up going
through a bunch of tapes.
This is Amanda 3.3.9 on Ubuntu 14.04 with LTO6 and 2TB of holding disk as two
1TB enterprise SSDs.
I realize I can work around this with configuration and by watching what's going on with my servers
and Amanda, but I also think this should be classified as a bug. Amanda should know that it is not
going anywhere and isn't going to accomplish anything by waiting. The admin can't do anything to fix
it either. It has to be terminated. So, Amanda should terminate and send a report.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geosciences Departments
(*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
