>... I *believe* I'm seeing a situation where while
>running amdump, a check with amstatus shows that while one of my large
>fs's is taping from holding disk, the fs's that have not dumped yet are
>NOT being dumped even though I have plenty holding disk available, then
>after the tape job completes the dump starts again. ...
First, you should never assume amstatus is telling the whole truth.
It only looks at the amdump file, which is not locked and messages can
get garbled.
Having said that, I'd start looking at the file by hand near the time
of the taper start for the big fs and see what it says is going on that
it cannot start another dump.
>I think John had a
>perl script that would take an amdump files and convert the time stamps?
ftp://gandalf.cc.purdue.edu/pub/amanda/amdumpts
>George Kelbley
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
