Red Hat Bugzilla – Bug 150322
portmap needed on nfs client to mount nfs filesystem but not documented
Last modified: 2007-11-30 17:07:06 EST
Description of problem:
The documentation for RHEL 3 and 4 say that to mount a NFS filesystem
mount shadowman.example.com:/misc/export /misc/local
However if portmap is not running on the client the mount will take
five minutes (it does succeed however and access to filesystem works
as expected afterwards). After portmap is started the mount takes the
expected amount of time (< 1s)
The documentation does not mention that portmap should be running on
the client. In the case of a "one off" mount on a client that does
not normally run the portmapper the behaviour is bad.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mount shadowman.example.com:/misc/export /misc/local
Mount succeeds after five minutes.
Mar 3 15:56:23 clienthostname kernel: portmap: server localhost not
responding, timed out
Mount succeeds in timely fashion.
I think it would be hard to try and document every single
failure or hang case. As I will agree is very annoying to
have a mount hang for mins before failing, I feel the real
problem is why is the portmapper not coming up or why
is it dying....
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.