you could use kill -17 to stop it (prevent it from being scheduled) and
kill -19 to wake it up again
then you can see if wait-time drops


Raix RS wrote:
> I performmed the nmon command.
> Used K Set Text Data I/O Use io other repage
> 27048 5.0 6040 5336 472 4864 0 1% 11 0 0
> fileserver
> 24784 1.5 40320 40172 4 40168 0 8% 0 0 0 java
> 3140 0.5 412 36 4 32 0 0% 0 0 0 syncd
> 1916 0.0 504 68 20 48 0 0% 0 0 0 qdaemon
>
> I looked at the fileserver process (27048) which has considerable io
>
> ps -ef|grep 27048
> UID PID PPID C STIME TTY TIME CMD
> root 27048 8884 10 Aug 17 - 233:10
> /usr/afs/bin/fileserver
> Looking at this line I can see this process is cpu intensive and has a
> scheduling penalty of C=10
> Also this process is concerned with afs. This one could very well be
> it.
>
> A software call with ibm support has also been made. I'm curious to
> see how they plan to tackle this problem. Therefore I will wait before
> restarting this process.
>
> I'll will post the outcome/results once I have them.
>
> Raix.