Jurjen Oskam wrote:

> Rebooting is the easiest and most sure way of getting rid of the process.
> However, if you know what the process is (was) doing, there are some other
> things you might try. For example, if the process was writing something
> to a SCSI-tape, you might try to turn off the particular drive and hope
> that there's a timeout in the device driver, which will in turn cause the
> system call your process is hanging in to return and thus the SIGKILL to
> be delivered, killing the process. Other infamous cases are processes
> accessing files over an NFS mount when the NFS mount suddenly disappears
> due to e.g. a network problem. In that last case however, there are mount
> options you can use to prevent hanging uninterruptable processes.
>
> However, always be careful: things like this can also occur with faulty
> hardware and/or kernel and/or device driver. Fiddling with things might
> make matters worse. Properly shutting down all normal processes and then
> reboot is most likely the safest path to follow.
>
Thanks. Shutdown of apps and after a reboot eveything was fine again.
Cause was I/O problems on the san. Process was probably waiting for
uninterruptible I/O system call and didn't return.
Rgds, Gert