On Fri, Nov 25, 2011 at 07:34:56AM +0000, Ken Moffat wrote: > On Thu, Nov 24, 2011 at 10:18:34PM +0000, Ken Moffat wrote:
> In fact, the longest part was banging my head against the wall > while testing :-( It's working now, but along the way the results > were very intermittent and iffy - a lot of the old 'getfh failed' > messages in the server logs (i.e. "something is wrong somewhere"), > mostly fixed by rebooting the server. This is with an old client on > an LFS-6.7+ system using portmap. > > ISTR that my previous tests of nfs setups tended to be equally > problematic, so perhaps it's all as good as ever. However, there > are two points worth noting here: > Realised I'd left in my sed for the server bootscript, to take out the "only in 2.6" nfsd. Since everyone with LFS-7.0 is using a 3.x kernel, I tried using the original script and *enabling* this part - as expected, error messages about nfsd. Oh, and back to the 'getfh failed: function not implemented" message from mountd. This was NOT fixed by stopping nfs-server, correcting the script, and (re)starting nfs-server. What did fix it was running 'exportfs -ra' and then bouncing the server. So, I'm wondering if it will work better with 'exportfs -ra' as the first stage of starting the server ? In theory, that should only be necessary during changes... But, since we *are* using 3.x kernels (and in any case the nfsd part doesn't work on recent 2.6 - see my earlier comments on bringing up my LFS-6.8 server in -support) I think the parts that mount and umount /proc/fs/nfsd should be dropped. Comments welcome. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
