Red Hat Bugzilla – Bug 1276538
[exportfs] exportfs -u cannot unexport when the specified path involves a trailing "/"
Last modified: 2017-03-21 07:23:06 EDT
+++ This bug was initially created as a clone of Bug #1276534 +++ Description of problem: When using "exportfs -u" to unexport just one directory, it always failed when the specified path involves a trailing "/", with error: exportfs: Could not find 'client.example.com:/export/' to unexport. Version-Release number of selected component (if applicable): nfs-utils-1.2.3-64.el6 How reproducible: 100% Steps to Reproduce: 1. exportfs -v $HOSTNAME:/export/ 2. exportfs -u client2.example.com:/export/ Actual results (for RHEL6): [root@ibm-x3650m4-08 ~]# exportfs -o rw,sync $HOSTNAME:/export/ [root@ibm-x3650m4-08 ~]# exportfs -v /export ibm-x3650m4-08.rhts.eng.pek2.redhat.com(rw,wdelay,root_squash,no_subtree_check,sec=sys,rw,root_squash,no_all_squash) [root@ibm-x3650m4-08 ~]# exportfs -u ibm-x3650m4-08.rhts.eng.pek2.redhat.com:/export/ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ failed [root@ibm-x3650m4-08 ~]# echo $? 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ should not return 0 as bz 1276221 said [root@ibm-x3650m4-08 ~]# exportfs -v /export ibm-x3650m4-08.rhts.eng.pek2.redhat.com(rw,wdelay,root_squash,no_subtree_check,sec=sys,rw,root_squash,no_all_squash) [root@ibm-x3650m4-08 ~]# exportfs -u ibm-x3650m4-08.rhts.eng.pek2.redhat.com:/export ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ success without trailing "/" [root@ibm-x3650m4-08 ~]# echo $? 0 [root@ibm-x3650m4-08 ~]# exportfs -v [root@ibm-x3650m4-08 ~]# rpm -q nfs-utils nfs-utils-1.2.3-64.el6.x86_64 [root@ibm-x3650m4-08 ~]# Expected results: Unexport success Additional info:
Moving to VERIFIED according to Comment #3. And will include this automatic case as regression test.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0741.html