Broken NFS server (or client?)

[Mark Street]

Good point....I knew we were headed here as I mentioned this to Linc last 
week.  I have rolled several 2.4.8 kernels in the last few days and am 
quite familiar with the options for the nfs daemon and client as well as 
version 3 support in the kernel.  How about a peek at the kernel config for 
the server and the client kernels?  That might cut down on some of the 
myriad of gremlins that "might" be going on here.

At 06:33 PM 8/12/2001 -0700, ME wrote:
>I feel uneasy asking you this question, because you seem to have done so
>many other things right, but I'll ask it anyway: are you sure that you are
>using the new kernel you compiled with knfsd support *and* client based
>nfs support too? (modified lilo.conf and rebooted with the new kernel
>actually showing up, etc.) (Please dont take offense, I just want to
>eliminate it from the realm of possible problems.)
>
>Your disk based client station should at least have nfs listed in
>/proc/filesystems as that is a list of filesystems that kernel can
>mount. I am not 100% certain, but think you could probably have your
>server not have client nfs support and still export nfs, but I dont see
>any reason for that. If it appears after you have an nfs service point
>mounted, then there is a chance that you have your nfs client set up as a
>module and it is being inserted and removed as you use it and no longer
>need it, but that seems unlikely unless you have some sort of crontab
>thing for removing it.