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.
Bug 1413828 - [ppc64le] Failed to mount nfs as cannot negotiate lower nfs version 3 with server
Summary: [ppc64le] Failed to mount nfs as cannot negotiate lower nfs version 3 with se...
Keywords:
Status: CLOSED DUPLICATE of bug 1415024
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.3
Hardware: ppc64le
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-17 04:58 UTC by Xujun Ma
Modified: 2017-02-10 10:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 19:01:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1415024 0 urgent CLOSED [uninitialized struct] get wrong nfs version when doing nfs mount 2021-02-22 00:41:40 UTC

Internal Links: 1415024

Description Xujun Ma 2017-01-17 04:58:17 UTC 
Description of problem:
Failed to mount nfs

Version-Release number of selected component (if applicable):
nfs-utils-1.3.0-0.35.el7.ppc64le
nfs-utils-1.3.0-0.34.el7.ppc64le
kernel:3.10.0-541.el7.ppc64le




How reproducible:
100%

Steps to Reproduce:
1.Use mount cmd to mount a  nfs:
2.
3.

Actual results:
failed to mount nfs with error：
mount.nfs: Protocol not supported
mount.nfs: requested NFS version or transport protocol is not supported


Expected results:
mount nfs successfully

Additional info:
no problem with nfs-utils-1.3.0-0.33.el7.ppc64le
ppc only
Comment 1 Yongcheng Yang 2017-01-17 05:48:40 UTC 
As Bug 1375259 mentioned, it changes to start the mounting process at 4.2 since nfs-utils-1.3.0-0.34.el7. However this failure seems to mounting with an UN-supported nfs version.

Please provide the detailed "Actual results" logs on the nfs client side especially the mount options used.

Also on nfs server, please log:
# exportfs -v
# cat /proc/fs/nfsd/versions
Comment 8 Steve Dickson 2017-02-01 19:01:12 UTC 
This seems to work for me 

# mount -vvv 127.0.0.1:/home /mnt/tmp
mount.nfs: timeout set for Wed Feb  1 14:00:43 2017
mount.nfs: trying text-based options 'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=127.0.0.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 127.0.0.1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 127.0.0.1 prog 100005 vers 3 prot UDP port 20048

# rpm -q nfs-utils
nfs-utils-1.3.0-0.35.el7.ppc64

Please check your tests to see why false positives are happening
Comment 9 Yongcheng Yang 2017-02-10 09:48:06 UTC 
(In reply to Steve Dickson from comment #8)
> This seems to work for me 
> 
> # rpm -q nfs-utils
> nfs-utils-1.3.0-0.35.el7.ppc64
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Please notice it's the ppc64le but not ppc64.

Maybe it's worth another try with arch "ppc64le".
Note You need to log in before you can comment on or make changes to this bug.