Red Hat Bugzilla – Bug 113138
Can't export file systems nfs mount on solarisI
Last modified: 2007-11-30 17:07:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Description of problem:
I cannot seem to nfs mount filesystems from this machine on my solaris
5.8 machine. I get the following error message:
nfs mount: cvs.raddns.net: : RPC: Unable to receive
nfs mount: retrying: /mnt/cvs/hdd1/release
After this happens, it seems that mountd has died because when I do:
service nfs restart
it says "failed" when trying to stop mountd
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.export file systems from EI linux
2.attempt to mount on sunos
Turns out there was a bogus reverse map (ip->name) in dns for the
client. Adding the correct mapping in the server's host file made
things work. But mountd shouldn't die in this circumstance.
All it means when it fails to stop mountd is that it was not started;
not that the start failed. It may simply not have ever managed to
start. Closing, since you tracked down the problem.
There really still is a problem. After a client with a bogus reverse
IP map tries to mount a filesystem from the server, the server get
wedged and won't export to any client, even one with a valid
service nfs restart unwedges until the next such request.
1. NFS server should be able to survive even if it doesn't grant the
remove mount request.
2. There should be a way to tell it to go ahead and grant such requests.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
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.