Red Hat Bugzilla – Bug 52281
Reboot of NFS server is too slow if former clients are down
Last modified: 2007-04-18 12:36:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808
Description of problem:
When an NFS server is rebooted, it may take a very long time to restart the
NFS service and come back to life.
I suppose it attempts to contact clients that had filesystems mounted from
it at the time of the boot, but it appears to do so sequentially, and with
a very large time-out for each client.
If a server serves a lot of machines configured to dual-boot Red Hat Linux
and MS-Windows, as in some labs at the university, it may take a very long
time to reboot while it attempts to contact each client, particularly those
that are running MS-Windows at the time of the server reboot, but that had
some filesystem mounted from the server while running Red Hat Linux that
may not have been properly unmounted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Set up an NFS server for a couple of labs of dual-booted Red Hat
2.Let the labs run for a while.
3.Reboot the server.
4.Wait a long time (more like hours than minutes) for NFS server to restart.
5.Give up and reboot the server again (I'm not sure it makes any
difference, but it appears that the second reboot was faster).
Actual Results: The server takes too long to restart the NFS service when
former clients are down or running another OS that doesn't understand NFS RPCs.
Expected Results: NFS should recover faster.
Its up to the clients to retry, not the server to inform them
its now up. But the reboot speed seems to have gotten better in later