In regard to: Re: [Networker] Stuck tape, Stan Horwitz said (at 9:31pm on...:

>On Wed, 13 Nov 2002, Adkisson, Christopher wrote:
>
>> I get this on a UNIX platform, NW 5.5.x.  I simply discover the nsrmmd
>> process associated with that drive and terminate it.
>>
>> # fuser /dev/rmt/?cbn
>> produces PID
>> # kill -9 PID
>
>Thanks, but as I said before, fuser does not reveal anything in this case.
>I could start going by trial and error, but that would kill off active
>devices' nsrmmd processes so I think I will have to wait 'til tomorrow and
>reboot the system, esp. since its been nearly four weeks since the
>previous reboot.

Stan-

It's in situations like this (NetWorker "stuck" accessing a tape drive)
where doing a proper shutdown:

        /sbin/init.d/NSRstartstop stop

caused media database corruption for us on 3 separate occassions under
6.1.1.  Our server is also Tru64 UNIX 4.0f.  Reports from another
gentleman on the list indicated that he has seen the same problem on
Solaris at 6.1.1.

It hasn't happened since we upgraded to 6.1.2, but then again I haven't
had a problem with NetWorker thinking it was accessing a tape when it
wasn't since upgrading to 6.1.2 either.

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=