Bug 436630 - mount.nfs4 look for the wrong address of an multihomed nfs server
mount.nfs4 look for the wrong address of an multihomed nfs server
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Steve Dickson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-08 12:24 EST by Jean-Jacques Sarton
Modified: 2009-01-09 01:08 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 01:08:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jean-Jacques Sarton 2008-03-08 12:24:12 EST
Description of problem:

If the nfs server is multihomed and the ip address choosed by the client
may be wrong. mount.nfs4 will always choose the first address returned by
gethostbyname(). If the server is not reachable above the one address mounting
of the nfs share will fail. If the wrong IP is choosed the performance will not
be optimal.

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

How reproducible:
near very good with maradns as DNS server

Steps to Reproduce:

1. assign 2 address to the server, eg sv.example and sv.example
2. mount the share and show with mount which IP was used. if the ip is OK, try
again, if always OK try to mount sva.example (a non existant host) and then try
again with the correct server name. 

Actual results:

the choosed address is always the first address returned by the DNS server.

Expected results:
If one of the addresses returned by  gethostbyname() is in the same network
as the client (eg client io = choose always the ip

Additional info:
Comment 1 Bug Zapper 2008-11-26 05:04:33 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 2 Bug Zapper 2009-01-09 01:08:09 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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