Bug 1002418 - when disable tcp in mountd, umount.nfs fail with no output.
Summary: when disable tcp in mountd, umount.nfs fail with no output.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: nfs-utils
Version: 5.9
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-29 07:29 UTC by JianHong Yin
Modified: 2014-02-05 22:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:17:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description JianHong Yin 2013-08-29 07:29:05 UTC
Description of problem:
when disable  tcp in mountd, umount.nfs fail with no output.

Version-Release number of selected component (if applicable):
nfs-utils-1.0.9-66.el5
nfs-utils-1.0.9-69.el5

How reproducible:
always

Steps to Reproduce:
1. echo 'RPCMOUNTDOPTS="--no-tcp"' >>/etc/sysconfig/nfs;
   echo '/tmp *(rw)' >/etc/exports
2. service nfs restart
3. mount localhost:/tmp  /media
   umount.nfs  /media
   echo $?

Actual results:
[root@dhcp-13-16 ~]# umount.nfs /media -vvv
mount: Unable to connect to 127.0.0.1:0, errno 111 (Connection refused)
[root@dhcp-13-16 ~]# umount.nfs /media -vvv  -f   #and -f can umount success
localhost:/tmp umounted

Expected results:
umount success

Additional info:

Comment 1 RHEL Program Management 2014-01-29 10:35:06 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 2 RHEL Program Management 2014-02-05 22:17:08 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.