Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionWeston Andros Adamson
2012-09-06 20:16:53 UTC
Description of problem:
If you mount server-a:/export, but that is referred to server-b:/export, you
are unable to unmount that mountpoint!
# umount /mnt
/mnt was not found in /proc/mounts
/mnt was not found in /proc/mounts
# echo $?
32
The issue seems to be that /proc/mounts has the address of the referred server,
not the server originally mounted (or shown in output of "mount", "df").
I tracked this down to an issue in nfs-utils-1.2.3-15's utils/mount/nfsumount.c
that has been fixed upstream by this commit (i think): dc08c702a6c7f824f317af561f491635ee898a71.
I say "i think" because I was unable to get the tag 'nfs-utils-1-2-3' to compile
on our RHEL 6.2 machines, but when I replaced /sbin/umount.nfs with one from
the 'nfs-utils-1-2-4' tag everything worked!
Steve - Feel free to ping me if you need any more info (as always).
Version-Release number of selected component (if applicable):
1.2.3-15
How reproducible:
quite reproducible, but only with this version of nfs-utils. nfs-utils from
RHEL 6.1, 6.3 do not have this problem, nor does any recent nfs-utils.
Steps to Reproduce:
1. set up 2 nfs servers, one referring it's rootfs to the other
2. on the client, mount the first server
3. try to unmount
Actual results:
umount returns non zero, outputs errors, doesn't unmount
Expected results:
umount should work!
Additional info:
commit dc08c702a6c7f824f317af561f491635ee898a71
Author: Chuck Lever <chuck.lever>
Date: Wed Oct 13 13:55:10 2010 -0400
umount.nfs: Distinguish between nfs4 and nfs mounts