I have attached a strace of nfs.mountd. Thanks
---------------------------------------- > From: [email protected] > To: [email protected] > Date: Thu, 24 Jul 2014 21:35:14 -0400 > Subject: Re: [blfs-dev] NFS rpc.mountd segfault and unable to end nfsdcltrack > grace period > > Okay, well I removed NFS v4 support and recompiled the kernel. It got rid of > the NFSD complaints and grace period problem, but rpc.mountd still segfaults > at 0 ip 084ff46 when I attempt a remote mount. Something must be in need of a > patch. > > Thanks for your help, I feel like we are getting close. > > ---------------------------------------- >> Date: Thu, 24 Jul 2014 19:22:07 +0100 >> From: [email protected] >> To: [email protected] >> Subject: Re: [blfs-dev] NFS rpc.mountd segfault and unable to end >> nfsdcltrack grace period >> >> On Thu, Jul 24, 2014 at 01:38:51AM -0400, The Lightning Stalker wrote: >>> NFS gives these console messages during system boot. >>> >> >> I am not sure if your two problems below are connected, or not. >> >>> [ 7.926298] NFSD: the nfsdcld client tracking upcall will be removed in >>> 3.10. Please transition to using nfsdcltrack. >>> [ 7.926465] NFSD: starting 90-second grace period (net c196ea80) >>> . . . >>> [ 128.352059] NFSD: Unable to end grace period: -110 >>> >> >> Google suggests that is an NFSv4 message. My server runs v3 (on >> 3.10 at the moment, with LFS-7.4) and I do not have any problem >> mounting its shares from recent desktops - my most recent desktop >> build used LFS-svn-20140514, which is now getting rather old :-( >> My desktops do not enable CONFIG_NFSD : in the past I have had both >> client and server running on a desktop, for testing, and the >> combination of the two is definitely valid. >> >>> If I try to mount a share, rpc.mountd segfaults. >>> >>> [ 542.947761] rpc.mountd[1687]: segfault at 0 ip 0804ff46 sp bfa97880 error >>> 4 in rpc.mountd[8048000+18000] >>> >>> It is a fresh build of ALFS trunk 10626 (2014-07-08). Everything else is >>> working perfectly. >>> >>> NFS-Utils was built and rebuilt according to the book, all nfs options are >>> enabled in the kernel, nfsd kernel module built and running >>> >>> After some searching, it appears that these issues have been encountered >>> before with NFS, although not exactly like this. It appears something in >>> the kernel or in one of the NFS packages requires patching, which is above >>> my current skill level. >>> >>> Thanks >> >> I don't think the BLFS book handles nfs v4 : you might need >> additional packages. Alternatively, if you are only using v3 (or >> v2), try removing the v4 kernel options. >> >> ĸen >> -- >> Nanny Ogg usually went to bed early. After all, she was an old lady. >> Sometimes she went to bed as early as 6 a.m. >> -- >> http://lists.linuxfromscratch.org/listinfo/blfs-dev >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page > > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page
trace
Description: Binary data
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
