>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 the holding disk)? If they are going through the
holding disk, it could be normal for the tape to be idle waiting on
something to do.
What happens if you do something like this:
/sbin/dump 0f - > /dev/null /
or this:
/sbin/dump 0f - / | rsh localhost "cat > /dev/null"
What version of dump are you using? You really, really, really want
to get the latest stuff from sourceforge. It was reportedly pretty bad
for a while but has gotten a good maintainer now and is much better.
>These are some typical error from the log:
>...
Clearly the dumps are getting started and moving some data, so something
must be freezing up. I'm not sure how to track this down other than to
try and catch it in the act and run gcore on the various programs and
then a debugger to see what they are waiting on.
>Hien Viet Lieu
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
