I finally got around to moving from 2.1.122, and went to 2.1.128. It's been a while since I moved, and I had to redo my kernel config options from scratch. Anyway, unless I forgot something stupid, it seems that the NFS client breaks in 2.1.128 even with maxcpus=0. Once you try to read a file from filesystem (say, a file 'cat' or running 'more') the process goes into the 'D' state, and seems to become un-killable. The file system directory structure is perfectly visible. Background: I am running the Redhat 5.1+errata versions of NFS server and friends. I have tried NFS mounting both a local loopback (using CFSd) and an NFS export from a 2.0 redhat4.2 system. For now, I am going back to 2.1.122 since it has worked just great for me. ----------------- Brian Curnow ----------------
