Bug 718063 - double mounted nfs entries for both ipv4 and ipv6
double mounted nfs entries for both ipv4 and ipv6
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Steve Dickson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-06-30 16:45 EDT by Rolf Fokkens
Modified: 2012-08-07 14:39 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-07 14:39:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fstab that results in double NFS mounts (656 bytes, application/octet-stream)
2011-06-30 16:47 EDT, Rolf Fokkens
no flags Details

  None (edit)
Description Rolf Fokkens 2011-06-30 16:45:27 EDT
Description of problem:
After upgrading to Fedora 15 all my NFS mounts are both done on IPv4 and IPv6. This means that all is mounted twice. I'm quite sure this was not the case on Fedora 15.

I suspect this is caused by the fact that IPv6 becomes available (radvd on server) after the first NFS mount, and before an apparent second NFS mount.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Enable IPv6 networking
2. Enter both an A and an AAAA record in DNS for the NFS server
3. Boot the Fedora 15 client that mounts NFS
Actual results:
[root@home07 init.d]# mount
/proc on /proc type proc (rw,relatime)
/sys on /sys type sysfs (rw,relatime,seclabel)
home01:/home/ on /home type nfs4 (rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=2001:1af8:fe43:2:218:f3ff:fefd:97a,minorversion=0,local_lock=none,addr=2001:1af8:fe43:2::1)
home01:/home/ on /home type nfs4 (rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,minorversion=0,local_lock=none,addr=
[root@home07 init.d]#

Expected results:
[root@home07 init.d]# mount
/proc on /proc type proc (rw,relatime)
/sys on /sys type sysfs (rw,relatime,seclabel)
home01:/home/ on /home type nfs4 (rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=2001:1af8:fe43:2:218:f3ff:fefd:97a,minorversion=0,local_lock=none,addr=2001:1af8:fe43:2::1)
[root@home07 init.d]#

Additional info:
Blaming nfs-utils might be unfair, as probably the whole systemd startup may cause the problem.
Comment 1 Rolf Fokkens 2011-06-30 16:47:55 EDT
Created attachment 510752 [details]
fstab that results in double NFS mounts
Comment 2 Fedora End Of Life 2012-08-07 14:39:41 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:

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