>I have it set to 1800 sec, yet amstatus is reporting a process has been
>"stuck" for ~1hr now:
>
>hub.org:da4s1a 0 211984k dumping 0k (0.00%)
>(0:41:03)
And you believed amstatus??? :-)
Amstatus is only reporting what gets put in the detailed amdump log file.
It is not, for instance, actually contacting any of the involved parties
(dumper, taper) to find out how far along they really are. In particular,
for direct to tape dumps, there are no log messages issued once the
operation starts, so there is no way to know (from the log) how far
along it is, and thus, amstatus cannot really say anything useful.
So my first guess is that this is what you are seeing. The dump is
actually still progressing but nothing is going in the log so amstatus
seems to be frozen. I have a note to myself to output some status
updates in taper at some time that amstatus could use, but it's pretty
low priority.
>is there one there that I could do a 'truss' on? use gcore to build a
>core file from? which one do I "associate" with the above 'dump'?
Read and understand the amdump file and all will be answered :-).
In general, you'll see a command go from driver to one of the dumpers
telling it to either run a dump into the holding disk (FILE-DUMP) or
direct to tape (PORT-DUMP). Take the dumper number and look at the
beginning of the log file for the matching PID for when it got started.
Then poke to your heart's content. I'd probably start with lsof on it
and watch the network file descriptor bytes transferred.
You could also run lsof on the writer side of taper (probably the higher
pid of the two) and watch the bytes written to the tape device.
Or you could just go look at the blinking lights on the drive :-).
>Marc G. Fournier
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
