Bug 1000979

Summary: umount.nfs -h option not supported
Product: Red Hat Enterprise Linux 6 Reporter: JianHong Yin <jiyin>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED WONTFIX QA Contact: Yongcheng Yang <yoyang>
Severity: medium Docs Contact: Milan Navratil <mnavrati>
Priority: low    
Version: 6.4CC: coughlan, eguan, salmy, steved, swhiteho, yoyang
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-07 22:49:44 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 JianHong Yin 2013-08-26 08:58:56 UTC
Description of problem:
umount -h option not supported

Version-Release number of selected component (if applicable):
[root@dhcp-13-188 ~]# umount.nfs -h
umount.nfs: -h: not found

[root@dhcp-13-188 ~]# umount.nfs -h
umount.nfs: -h: not found

[root@dhcp-13-188 ~]# rpm -q  nfs-utils
nfs-utils-1.2.3-36.el6.x86_64
[root@dhcp-13-188 ~]# lsb_release -sr
6.4

How reproducible:
always

Steps to Reproduce:
1. umount -h
2.
3.

Actual results:
[root@dhcp-13-188 ~]# umount.nfs -h
umount.nfs: -h: not found

Expected results:
usage: umount.nfs dir [-fvnrlh]
options:
        -f      force unmount
        -v      verbose
        -n      Do not update /etc/mtab
        -r      remount
        -l      lazy unmount
        -h      print this help


Additional info:

Comment 2 RHEL Program Management 2013-10-14 02:34:10 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.

Comment 3 Yongcheng Yang 2015-04-03 06:13:39 UTC
Also the USAGE should be print to user when using this command with wrong option, for example:

Actual results:
[root@hp-dl580g7-04 ~]# umount.nfs -xxx
umount.nfs: -xxx: not found

[root@hp-dl580g7-04 ~]# 

Expected results: 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ how it actually works in rhel7.1
[root@intel-s3e36-01 ~]# umount.nfs -xxx
umount.nfs: invalid option -- 'x'
usage: umount.nfs dir [-fvnrlh]
options:
	-f		force unmount
	-v	verbose
	-n	Do not update /etc/mtab
	-r	remount
	-l	lazy unmount
	-h	print this help

[root@intel-s3e36-01 ~]#

Comment 4 Steve Whitehouse 2015-12-11 18:23:46 UTC
Setting low priority on this, since it is not something that would normally be an issue for most users. We should look at doing this upstream, if it has not been done already, but I'm not sure that we necessarily need to do this in RHEL6.

Comment 5 Steve Dickson 2016-12-07 22:49:44 UTC
(In reply to Yongcheng Yang from comment #3)
> Also the USAGE should be print to user when using this command with wrong
> option, for example:
> 
> Actual results:
> [root@hp-dl580g7-04 ~]# umount.nfs -xxx
> umount.nfs: -xxx: not found
> 
> [root@hp-dl580g7-04 ~]# 
> 
> Expected results: 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ how it actually works in rhel7.1
> [root@intel-s3e36-01 ~]# umount.nfs -xxx
> umount.nfs: invalid option -- 'x'
> usage: umount.nfs dir [-fvnrlh]
> options:
> 	-f		force unmount
> 	-v	verbose
> 	-n	Do not update /etc/mtab
> 	-r	remount
> 	-l	lazy unmount
> 	-h	print this help
> 
> [root@intel-s3e36-01 ~]#
Well this is just the way RHEL6 works. Unlike RHEL7, RHEL6 assumes 
the given first give argument is the directory to unmount. If 
the argument does not start with '/' a "not found" error is
issued. The correct error code is used so I think we are fine.