Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMenny Hamburger
2013-03-05 10:43:57 UTC
Created attachment 705357[details]
When no port is supplied or port 2049 is supplied, add them to the mount options
Description of problem:
When mounting NFS with port 2049 (default), the port is not added to the mount options and as result we are not mapped to the correct port on the NFS server.
Version-Release number of selected component (if applicable):
Tried on Centos6.2 client but exists on later releases also.
How reproducible:
strace mount command with port=2049 and with other port:
When 2049 is given the port is not added to the mount command.
Actual results:
Mount on port other than 2049 in the NFS server.
Expected results:
Mount on port 2049 in the server
Comment on attachment 705357[details]
When no port is supplied or port 2049 is supplied, add them to the mount options
Removing patch - it should only use port 2049 when it is specifically supplied in the mount command.
Comment 4RHEL Program Management
2013-10-14 04:09:56 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This seems to work as intended on RHEL 6.5. 'mount -oport=2049 <IP>:<path> <path>' works and I was able to verify the connection with netstat; and mount with any other port number fails.
(In reply to Charles Rose from comment #5)
> This seems to work as intended on RHEL 6.5. 'mount -oport=2049 <IP>:<path>
> <path>' works and I was able to verify the connection with netstat; and
> mount with any other port number fails.
Well the default protocol version is V4 which requires mounts
to use port 2049.
Try adding the 'v3' mount option when using ports other an 2049
Created attachment 705357 [details] When no port is supplied or port 2049 is supplied, add them to the mount options Description of problem: When mounting NFS with port 2049 (default), the port is not added to the mount options and as result we are not mapped to the correct port on the NFS server. Version-Release number of selected component (if applicable): Tried on Centos6.2 client but exists on later releases also. How reproducible: strace mount command with port=2049 and with other port: When 2049 is given the port is not added to the mount command. Actual results: Mount on port other than 2049 in the NFS server. Expected results: Mount on port 2049 in the server