Bug 1394251

Summary: mount.nfs does not give failing option in error message
Product: Red Hat Enterprise Linux 7 Reporter: Jeremy Harris <jeharris>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED NOTABUG QA Contact: Yongcheng Yang <yoyang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: chunwang, eguan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-08 15:45:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeremy Harris 2016-11-11 13:28:11 UTC 
Description of problem:
 Mount failing with "mount.nfs: an incorrect mount option was specified" -
does not say exactly what option is incorrect, no there is little guidance on
what to change to fix it.

Version-Release number of selected component (if applicable):
  mount.nfs: (linux nfs-utils 1.3.0)


How reproducible:
  100%


Steps to Reproduce:
1. Attempt to set up nfs mount in fstab, with "default" as option field
2. Trigger mount, see error


Actual results:

[root@rhel7 ~]# mount -t nfs -v dom0:/home/jgh /dom0
mount.nfs: timeout set for Fri Nov 11 12:05:00 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.100.1,clientaddr=192.168.100.249'
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified



Expected results:
 More clue as to what's wrong
Comment 1 ChunYu Wang 2016-11-12 05:30:39 UTC 
(In reply to Jeremy Harris from comment #0)

Hi, Harris: 

[root@nfs ~]# mount -t nfs -v 10.73.4.163:/ /mnt/nfs_in/ -o addr=10.73.4.141,clientaddr=10.73.4.141
mount.nfs: timeout set for Sat Nov 12 00:27:16 2016
mount.nfs: trying text-based options 'clientaddr=10.73.4.141,vers=4,addr=10.73.4.163'

[root@nfs ~]# mount -t nfs -v 10.73.4.163:/ /mnt/nfs_in/ -o addr=10.73.4.141,clientaddr=10.73.4.141,rr
^^^^^^^^^^^^ When I use a wrong option `rr`
mount.nfs: timeout set for Sat Nov 12 00:27:53 2016
mount.nfs: trying text-based options 'clientaddr=10.73.4.141,rr,vers=4,addr=10.73.4.163'
mount.nfs: mount(2): Invalid argument
^^^^^^^^^^^ It returns `Invalid argument` due to the `rr`
mount.nfs: an incorrect mount option was specified
Comment 2 ChunYu Wang 2016-11-12 05:34:59 UTC 
(In reply to ChunYu Wang from comment #1)

With the last comment, this is not a bug, but it will be helpful, if the mount returns the wrong argument.
Comment 4 Steve Dickson 2017-04-08 15:45:59 UTC 
(In reply to ChunYu Wang from comment #2)
> (In reply to ChunYu Wang from comment #1)
> 
> With the last comment, this is not a bug, but it will be helpful, if the
> mount returns the wrong argument.

If a patch appears upstream to take care of this problem that would be good and we can open this back up...  but for now I'm going to close this as not a bug
Comment 5 Jeremy Harris 2017-04-10 08:25:34 UTC 
Perhaps we need a "requires upstream fix" reason for closure, since "not a bug"
is manifestly incorrect?
Comment 6 Steve Dickson 2017-04-19 16:52:27 UTC 
(In reply to Jeremy Harris from comment #5)
> Perhaps we need a "requires upstream fix" reason for closure, since "not a
> bug"
> is manifestly incorrect?
Yes, it would make sense to use that type of reason, if it existed ;-)