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.

Description of problem:

I ran into the following problem using SL6.2: 

If I mount a NFS4 dir like this
#cat /etc/fstab
[...]
10.10.70.9://raid_0 /9 nfs

then this results in 
#cat /etc/mtab 
[...]
10.10.70.9://raid_0 /9 nfs rw,vers=4,addr=10.10.70.9,clientaddr=10.10.70.43 0 0

and this 

#cat /proc/mounts
[...]
10.10.70.9:/raid_0/ /9 nfs4
rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,por
t=0,timeo=600,retrans=2,sec=sys,clientaddr=10.10.70.43,minorversion=0,local_
lock=none,addr=10.10.70.9 0 0

Due to the different handling of the // for NFS4, I cannot unmount the directory again. If I try then I get the error 
#umount /9
/9 was not found in /proc/mounts
/9 was not found in /proc/mounts

This problem doesn't occur with NFS3 shares because the corresponding /proc/mounts entry still contains //. 

My workaround is to remove // from the /etc/fstab and change /etc/mtab on all running systems by hand.

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.