Red Hat Bugzilla – Bug 184225
NFS server exported filesystem not mounted
Last modified: 2007-11-30 17:07:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Description of problem:
We have a NFS server based on NFS utils version nfs-utils-1.0.6-33EL. The server has following exported filesystem.
Now we have many linux clients which mounts the server exported filesystem at random. Out of this clients, few clients are unable to mount all filesystem. In some clients only 2 filesystem is avialable, in somecases it is 3 or 4 but not all. And this problem starts all of a sudden. Once you see this issue in a particular client, the problem remains evenif you reboot the client. The only way you can fix it is by changing the ip address of the client and then reboot it.
This has become a regular issue and it happens on any machine irrelavant on the version of the OS of the client. We tried to look into the details and found that somehow the server keeps track of the mounted machines (IP address) in /var/lib/nfs/rmtab and xtab files.
This has become a real pain for us
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Arbitrarily one client will start behaving like this at one point of time.
2.you could see that all the filesystem of the server is not available from the client machine
3.Even reboot will not help anyway
The only way to get rid of it si to change the ip address of the client machine.
Are there any error or warnings being logged in /var/log/messages on either the
server or client?
No there is no relevant message in the /var/log/message file
Would it be possible to get a binary tethereal network trace of this occurring
(i.e. on the server, ethereal -w /tmp/data.pcap host <client> )....
It is very bizarre that you have to reboot client to for it succeed in doing
Created attachment 130863 [details]
Data captured from ethereal
The captured data from the file server (machine name "shark" with IP
192.168.3.120) when the client was trying to access home3(machine name "cyan"
with ip 192.168.2.11)
This time except home3 all the other 8 exported home area were visible from
Is there any type of error message in /var/log/messages on the server?
No, ther is no error in /var/log/messages
I'm wondering if the problem is the server is so busy that is simply
drops the mount request which causes the client to fail, without retrying.
There has been some recent changes to the RHEL3 mount command that
will cause the mount to retry. So please update your util-linux to latest
RHEL3 version which I believe is util-linux-2.11y-31.18
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.