"John R. Jackson" wrote:
Thanks John, I think you are absolutely right to question the dump
program. ...
It's 0.4b19 version ...
Well, I'd be a lot happier if it was ancient so I could blame it :-).
I've read in this list that there is a Linux dump 0.4b20 out there, so
there might be
Thanks John, I think you are absolutely right to question the dump
program. The inconsistancy may be due to the dump command, but it's more
likely that the processes it depends on are the main cause, and I don't know
how to find out what these processes are.
Anytime a filesystem failed to
Thanks John, I think you are absolutely right to question the dump
program. ...
It's 0.4b19 version ...
Well, I'd be a lot happier if it was ancient so I could blame it :-).
You're right that that seems pretty recent, so it may not be the culprit.
The inconsistancy may be due to the dump
Anytime a filesystem failed to backup, the tapedrive seemed to be idle forever
until the READ_TIMEOUT period lapsed, i.e no activity shown.
That could be normal. Looking at the amdump.NN file, are the file
systems that time out being done with PORT-DUMP (direct to tape) or
FILE-DUMP (through
