Red Hat Bugzilla – Bug 173038
cannot start CFS at boot-time with 2.6.13 or 2.6.14 kernels
Last modified: 2007-11-30 17:11:16 EST
Description of problem:
Cannot start cfsd at boot-time with new 2.6.13 and 2.6.14 kernels.
Version-Release number of selected component (if applicable):
This has been verified on i686 platforms.
Steps to Reproduce:
1. Enable nfs with 'chkconfig nfs on'
2. Enable cfsd with 'chkconfig cfsd on'
4. Attach a CFS share with 'cattach'
Initial cfsd mount request at boot-time times out, and CFS is unusable for the
machine after the machine finally does boot -- the cattach command fails.
CFSD should start at boot-time, and users should be able to 'cattach' CFS shares
as soon as the machine boots.
This issue seems to coincide with the new kernel NFS stack that reports the
mysterious "NFSD: starting 90-second grace period" message.
As an experiment, I inserted a delay into the /etc/rc.d/init.d/cfsd script that
starts it *after* nfsd, and waits 90s before attempting to mount its /.cfsfs
directory. That didn't work.
I extended the timeout to 120s, and it started working.
This problem doesn't seem to affect autofs, which is the other NFS-dependent
service I'm starting at boot-time.
The problem also cannot be reproduced on an already-running system. I tried to
shutdown affected services:
autofs cfsd nfs rpcidmapd portmap
and remove NFS-dependent modules:
modprobe -v -d nfs
modprobe -v -d nfsd
Re-enabling the above services prints the same kernel message ("NFSD: starting
90-second grace period") but this time, cfsd starts up right away and the
'cattach' command works.
FC3 and FC4 have now been EOL'd.
Please check the ticket against a current Fedora release, and either adjust the
release number, or close it if appropriate.
Your friendly BZ janitor :-)
The cfs package has been dropped from Extras.