topic Re: fuser -k will not kill off process in Operating System - HP-UX

fuser -k will not kill off process

lawrenzo — Tue, 02 Mar 2004 08:37:36 GMT

Hello,

When writing a file to a device - the process hung and I cannot release the drive:

root @ hp38 : fuser -u /dev/rmt/14m
/dev/rmt/14m: 13359o(root)

root @ hp38 : fuser -k /dev/rmt/14m
/dev/rmt/14m: 13359o

root @ hp38 : fuser -u /dev/rmt/14m
/dev/rmt/14m: 13359o(root)

I attempted to kill the process and this still will not work.

can someone help.

thanks

Re: fuser -k will not kill off process

Pete Randall — Tue, 02 Mar 2004 08:41:18 GMT

This is pretty typical. When waiting for an I/O to complete, the kernel puts the process in a wait state. Until the kernel gets the interrupt telling it that the I/O is completed, the process is stuck there - you can't kill it. Unless you can figure out how to get the I/O to complete, you're not going to be able to get rid of this process without rebooting.

Pete

Re: fuser -k will not kill off process

Dave Hutton — Tue, 02 Mar 2004 08:41:21 GMT

If you ps -ef | grep 13359 what is the process?

Dave

Re: fuser -k will not kill off process

lawrenzo — Tue, 02 Mar 2004 08:56:43 GMT

the process has now died - it took some time

Re: fuser -k will not kill off process

lawrenzo — Tue, 02 Mar 2004 08:58:38 GMT

thanks you

Re: fuser -k will not kill off process

Sridhar Bhaskarla — Tue, 02 Mar 2004 09:00:44 GMT

Hi Lawrenzo,

Pete had the perfect answer. It might have not solved (and there is no magical answer to it) your issue immediately but it explained exactly why the process *took sometime* to die.

-Sri

Re: fuser -k will not kill off process

lawrenzo — Tue, 02 Mar 2004 09:32:36 GMT

further investigation showed the follwoing in the syslog.log

Mar 2 14:17:18 hp38 vmunix: SCSI TAPE: dev = 0xcd171000 I/O error during close

does this mean there are scsi errors to the tape (the drive is inside a robot)

ioscan shows the tape as claimed

Re: fuser -k will not kill off process

Rory R Hammond — Wed, 03 Mar 2004 14:18:25 GMT

Your process didn't die immediatly because the tape was probably rewinding. When the rewind completed the process died. Processes on tapes ussually takes a while to die.
The syslog entry sounds pretty normal for an interrupted tape process

Rory