Red Hat Bugzilla – Bug 194041
Weird problem with nfs-utils-1.0.5-3
Last modified: 2007-11-30 17:07:10 EST
Description of problem:
On eof our NFS server is having nfs version 1.0.5-3, though this is a stable
version, but I am expereincing failure of rpc.mountd deamon when the below
mention scenario is met.
Say there is a client machine with IP 192.168.1.10, its name in NIS is apple,
now the machine is accessing the NFS server properly.
Let say you have changed the IP address of this apple machine from
192.168.3.10 to say 192.168.1.11 and updated the NIS database, so that
whenever the any machine on the domain contacts apple machine it will resolve
But the NFS server rpc.mountd will fail and to rectify it, you have restart
the nfs server.
while restating you will find that mountd had already failed.
I have looked into the issue and found that some file in /var/lib/nfs/rmtab
which keeps the info of client mounted on the nfs server, so as far as I have
understood, the nfs server while running is somehow unable to recognize this
change and whole rpc.mountd fails.
But I am not cofirmed about this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Try updating your nfs-utils to the latest version since there was a bug fix
for something simlar to what your seeing...
to which version I should upgrade.
My server OS version is RHEL3. So if I update the nfs-utils to latest version,
would it create any other problem?
nfs-utils-1.0.6-44EL is the lasted RHEL3 version
Can you confirm, whether we can directly load this version on my nfs server.
My NFS server version is
Red Hat Enterprise Linux WS release 3 (Taroon)
Linux whale 2.4.21-4.ELsmp #1 SMP
Yes, nfs-utils-1.0.6-44EL will work with 2.4.21-4.ELsmp
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.