On Thu, 2003-07-10 at 21:21, Ted Manos wrote: > I do not believe that the problem is SFS, or that SFS is hung. SFS > continues to function perfectly normally when accessed from CMS. I also > don't *think* that it is the VMNFS server, as that appears to continue to > function normally for any/all other mount points it is serving, just not > the one that has hung. > > When I kill the originating process, and finally get it and all of its > spawn killed off, there still remain two of its spawn which I can not kill, > even from root, no matter what signal I try to use. The only way I am able > to reset everything to that mount point, so it can again be made > operational, is to completely shutdown and re-IPL that Linux instance, and > then re-mount all the NFS mount points. I do NOT have to do *anything* > whatever to VM, SFS or the VMNFS server.
This sure sounds like classic NFS-client-stuck-in-disk-wait behavior. This is also why NFS sucks, but that's neither here nor there. One thing I'd suggest: > I am running 31-bit Linux "2.4.7-SuSE-SMP #1 SMP Wed Oct 17 15:31:03 GMT > 2001 s390" under z/VM V4.3.0 (PUT 0301) on a 2064-1Cx IFL processor. Is this the latest and greatest patched kernel from SuSE? IIRC, SuSE likes to put the NFS server in the kernel, and so it's possible that this is a bug that has already been addressed. If it were *me*, I'd give it a shot with a 2.4.21 kernel and see what happened. Adam
