| 2014-11-11 22:05:45 |
Tyler Sable |
bug |
|
|
added bug |
| 2014-11-11 22:07:34 |
Tyler Sable |
description |
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=2620:72:0:8c00::11,clientaddr=fe80::250:56ff:fe8b:28d7'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
|
| 2014-11-11 22:18:43 |
Peter Matulis |
bug |
|
|
added subscriber Peter Matulis |
| 2014-11-14 20:05:41 |
Dave Chiluk |
nfs-utils (Ubuntu): assignee |
|
Dave Chiluk (chiluk) |
|
| 2014-11-14 21:27:15 |
Dave Chiluk |
attachment added |
|
Proposed debdiff https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391662/+attachment/4260754/+files/lp1391662.debdiff |
|
| 2014-11-14 21:27:24 |
Dave Chiluk |
nfs-utils (Ubuntu): importance |
Undecided |
Medium |
|
| 2014-11-14 21:27:30 |
Dave Chiluk |
nfs-utils (Ubuntu): status |
New |
In Progress |
|
| 2014-11-14 21:27:38 |
Dave Chiluk |
nominated for series |
|
Ubuntu Precise |
|
| 2014-11-15 00:26:30 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug precise |
amd64 apport-bug patch precise |
|
| 2014-11-15 00:26:38 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2014-11-17 16:42:44 |
Dave Chiluk |
tags |
amd64 apport-bug patch precise |
amd64 apport-bug cts patch precise |
|
| 2014-11-17 16:55:26 |
Dave Chiluk |
description |
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
[Impact]
When all the following exist
- mounting a server using hostname.
- the hostname resolves to both an ipv4 and ipv6 address
- the nfs server only supports nfsv4
Then.
* The nfs client will not fall back fo nfsv4, and will be unable to mount
the share.
* The following errors are printed in the logs.
"
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
"
[Test Case]
* Restrict to nfsv3 on Server by setting RPCNFSDOPTS="--no-nfs-version 4" in /etc/default/nfs-kernel-server
* Enable dns resolution for both ipv4 and ipv6 of the server.
* Export a directory from the server (export -a)
* Attempt to mount the nfs share from client
[Regression Potential]
* Upstream backport that still exists upstream.
[Other Info]
* Fix already exists in 2.6+ which means >trusty already have the fix.
__________________________________________________________________________
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
|
| 2014-11-18 15:11:48 |
Chris J Arges |
bug task added |
|
nfs-utils (Ubuntu Precise) |
|
| 2014-11-18 15:13:00 |
Chris J Arges |
nfs-utils (Ubuntu): status |
In Progress |
Fix Released |
|
| 2014-11-18 15:13:05 |
Chris J Arges |
nfs-utils (Ubuntu Precise): assignee |
|
Dave Chiluk (chiluk) |
|
| 2014-11-18 15:13:07 |
Chris J Arges |
nfs-utils (Ubuntu Precise): importance |
Undecided |
Medium |
|
| 2014-11-18 15:13:10 |
Chris J Arges |
nfs-utils (Ubuntu Precise): status |
New |
In Progress |
|
| 2014-11-18 15:13:14 |
Chris J Arges |
nfs-utils (Ubuntu): assignee |
Dave Chiluk (chiluk) |
|
|
| 2014-11-20 19:40:29 |
Dave Chiluk |
description |
[Impact]
When all the following exist
- mounting a server using hostname.
- the hostname resolves to both an ipv4 and ipv6 address
- the nfs server only supports nfsv4
Then.
* The nfs client will not fall back fo nfsv4, and will be unable to mount
the share.
* The following errors are printed in the logs.
"
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
"
[Test Case]
* Restrict to nfsv3 on Server by setting RPCNFSDOPTS="--no-nfs-version 4" in /etc/default/nfs-kernel-server
* Enable dns resolution for both ipv4 and ipv6 of the server.
* Export a directory from the server (export -a)
* Attempt to mount the nfs share from client
[Regression Potential]
* Upstream backport that still exists upstream.
[Other Info]
* Fix already exists in 2.6+ which means >trusty already have the fix.
__________________________________________________________________________
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
[Impact]
When all the following exist
- mounting a server using hostname.
- the hostname resolves to both an ipv4 and ipv6 address
- the nfs server only supports nfsv3
Then.
* The nfs client will not fall back fo nfsv4, and will be unable to mount
the share.
* The following errors are printed in the logs.
"
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
"
[Test Case]
* Restrict to nfsv3 on Server by setting RPCNFSDOPTS="--no-nfs-version 4" in /etc/default/nfs-kernel-server
* Enable dns resolution for both ipv4 and ipv6 of the server.
* Export a directory from the server (export -a)
* Attempt to mount the nfs share from client
[Regression Potential]
* Upstream backport that still exists upstream.
[Other Info]
* Fix already exists in 2.6+ which means >trusty already have the fix.
__________________________________________________________________________
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
|
| 2014-11-20 19:40:53 |
Dave Chiluk |
description |
[Impact]
When all the following exist
- mounting a server using hostname.
- the hostname resolves to both an ipv4 and ipv6 address
- the nfs server only supports nfsv3
Then.
* The nfs client will not fall back fo nfsv4, and will be unable to mount
the share.
* The following errors are printed in the logs.
"
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
"
[Test Case]
* Restrict to nfsv3 on Server by setting RPCNFSDOPTS="--no-nfs-version 4" in /etc/default/nfs-kernel-server
* Enable dns resolution for both ipv4 and ipv6 of the server.
* Export a directory from the server (export -a)
* Attempt to mount the nfs share from client
[Regression Potential]
* Upstream backport that still exists upstream.
[Other Info]
* Fix already exists in 2.6+ which means >trusty already have the fix.
__________________________________________________________________________
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
[Impact]
When all the following exist
- mounting a server using hostname.
- the hostname resolves to both an ipv4 and ipv6 address
- the nfs server only supports nfsv3
Then.
* The nfs client will not fall back to nfsv3, and will be unable to mount
the share.
* The following errors are printed in the logs.
"
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
"
[Test Case]
* Restrict to nfsv3 on Server by setting RPCNFSDOPTS="--no-nfs-version 4" in /etc/default/nfs-kernel-server
* Enable dns resolution for both ipv4 and ipv6 of the server.
* Export a directory from the server (export -a)
* Attempt to mount the nfs share from client
[Regression Potential]
* Upstream backport that still exists upstream.
[Other Info]
* Fix already exists in 2.6+ which means >trusty already have the fix.
__________________________________________________________________________
If you attempt to mount a share from a server that is dual stack (i.e. has both an A and a AAAA record in DNS) and NFSv3-only, mount.nfs goes into an infinite loop of retrying an NFS-v4 mount:
mount nfs-v3-server:/path /mnt -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Nov 11 14:25:34 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=xxxx:xxxx::xxxx,clientaddr=xxxx:xxxx::xxxx'
mount.nfs: mount(2): No route to host
If we "hide" the AAAA record by setting an override in /etc/hosts, then mount.nfs correctly retries with NFSv3:
mount -t nfs nfs-v3-server:/path /mnt -v
mount.nfs: timeout set for Tue Nov 11 15:01:35 2014
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=x.x.x.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying x.x.x.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying x.x.x.x prog 100005 vers 3 prot UDP port 635
nfs-v3-server:/path on /mnt type nfs (rw)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Nov 11 15:56:25 2014
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
MarkForUpload: True
ProcEnviron:
SHELL=/usr/bin/ksh
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to precise on 2013-10-07 (400 days ago) |
|
| 2014-11-20 19:53:17 |
Brian Murray |
nfs-utils (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2014-11-20 19:53:19 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-11-20 19:53:21 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2014-11-20 19:53:23 |
Brian Murray |
tags |
amd64 apport-bug cts patch precise |
amd64 apport-bug cts patch precise verification-needed |
|
| 2014-11-20 20:19:40 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/nfs-utils |
|
| 2014-11-20 21:09:25 |
Dave Chiluk |
tags |
amd64 apport-bug cts patch precise verification-needed |
amd64 apport-bug cts patch precise verification-done |
|
| 2014-11-25 15:52:38 |
Marc Deslauriers |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2014-12-02 15:43:51 |
Launchpad Janitor |
nfs-utils (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2014-12-02 15:43:56 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
