I've also seen this before on both tape and staging devices.
A "kill -TERM <pid>"  of the appropriate process usually
works. As for the staging devices you need to use
"fuser /stagingdir/*" to see which processes have files in
the staging directory open[1]. The nsrmmd process doesn't
chdir() to the staging directory in order to use it, so
fuser won't find it given simply the directory name. If I'm
remembering correctly the nsrmmd process has only had the
volume file open when I've seen this on staging devices.

[1] - If your staging device is mounted on it's own filesystem
      you could use "fuser -c /stagingdir", see the man page.

> Date:    Mon, 21 Oct 2002 08:35:03 -0600
> From:    Robert Legate <rlegate AT SHAW DOT CA>
>
> I'm not exactly sure what your getting at with your message,
> however I do come across the "ready for writing, idle" message
> all the time on our DLT8000's.  It usually indicates a hung
> drive and the problem can be fixed by executing the "fuser"
> command i.e   # fuser /dev/rmt/0cbn where 0cbn us your affected
> device. This gives you the pid of the process that has hung the
> drive and killing that process (kill -9 [pid] ) will un-hang it.
> We also come across this message on file systems we use for
> staging, but the fuser command returns no pid. In this case
> we have to resort to re-starting networker. We are running
> 6.1.2 on Solaris 8.
>
> Rob Legate
> 780-493-2625
> 780 493-6540 cell

--
Mike Golub                                 Raytheon Technical Services
GIS Product Specialist(ConITS/CIPO)        NASA Langley Research Center
m.s.golub AT larc.nasa DOT gov                    Mail Stop 445, B1209T8 rm 809
voice:(757)864-4128  fax:(757)864-8463     Hampton, VA 23681-0001

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=