autofs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christof Koehler <christof.koehler@bccms.uni-bremen.de>
To: autofs@vger.kernel.org
Subject: Re: autofs reverts to IPv4 for multi-homed IPv6 server ?
Date: Mon, 11 Apr 2016 18:35:13 +0200	[thread overview]
Message-ID: <20160411163513.GC15079@bccms.uni-bremen.de> (raw)
In-Reply-To: <20160411163241.GB15079@bccms.uni-bremen.de>

Oops, replace 0.25.2 by 0.2.5 ... Sorry.

On Mon, Apr 11, 2016 at 06:32:41PM +0200, Christof Koehler wrote:
> Hello,
> 
> I will try to consolidate the answer in a single email without messing
> up the quoting too much.
> 
> > But we can't really start to work out what needs to be done unless
> > libtirpc is being used.
> 
> > And I think the best chance is to use 5.1.1 and possibly back port any
> > changes.
> 
> > As I say, the only other thing we can do is add some targeted debug
> > logging and see if we can spot what is going wrong.
> 
> I will then stick to the plan to defer this
> until ubuntu 16.04 has been released which should contain autofs 5.1.1
> and libtirpc 0.25.2. From the libtirpc git repo and the sourceforge page
> I see that 0.25.2 is from 2014, but not even debian unstable is
> using a newer version (and from the changelog things like gss_api
> support are the main changes ?). 
> 
> I will use a virtual machine with ubuntu 16.04 (or if preferable debian 
> testing or unstable) and then start experimenting. In that environment we 
> can do to autofs and also libtirpc (and nfs-common if necessary) whatever 
> is needed to get the necessary information. 
> 
> I will let you know when I start with that and what the baseline with
> the original packages of the distribution and simple rebuild of autofs
> --with-libtirpc is.
> 
> >> Apr  8 18:05:25 core324 automount[963]: get_nfs_info: called with host
> >> core330(fd5f:852:a27c:1261:2000::118) proto 6 version 0x40
> >> Apr  8 18:05:25 core324 automount[963]: get_nfs_info: called with host
> >> core330(2001:638:708:1261:2000::118) proto 6 version 0x40
> >> Apr  8 18:05:25 core324 automount[963]: mount(nfs): no hosts available
> 
> > Sadly that doesn't tell us much either, only that the rpc communication
> > has failed to get a result in some expected way.
> 
> Well, at least it shows that this autofs built at least is somehow aware of
> all the different IP adresses and trying the IPv4 one first. Of course
> no other conclusions can be drawn from this.
> 
> > That's right, as I say the RPC communication isn't failing in an
> > unexpected way so we aren't seeing any error messages.
> > 
> > About all that can be done is to add a patch that adds some extra
> > logging to try and get to the bottom of it.
> 
> That should be possible with a virtual machine as mentioned above.
> 
> > The first thing that stands out is that if libtirpc is not being used
> > all IPv6 hosts will be ignored because (my impression is that) glibc RPC
> > doesn't support IPv6.
> 
> The libtirpc documentation says that libtirpc is needed for IPv6 ready
> rpc support, http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php as
> linked from sourceforge.
> Might even be that glibc does actually no longer contain any rpc
> functionality ?
> https://archives.gentoo.org/gentoo-dev/message/186be8dc9753d18aafc9a5a616b3b991
> This would be supported by information on the tirpc web page mentioned
> above.
> 
> As far as I understand your analysis you are saying the IPv6
> mount in the "2001" case is just working by accident, right ?
> 
> > It's mount.nfs(8) mounting from the IPv6 address (when given a host name
> > not an address) in the former case and not autofs that's getting you an
> > IPv6 mount. And, AFAICS, the mount.nfs your using does use libtirpc.
> Yes.
> # ldd /sbin/mount.nfs4|grep tirpc
>         libtirpc.so.1 => /lib/x86_64-linux-gnu/libtirpc.so.1 (0x00007ffff7d9d000)
> and libtirpc is a hard package dependency of nfs-common.
> 
> Best Regards
> 
> Christof
> -- 
> Dr. rer. nat. Christof Köhler       email: c.koehler@bccms.uni-bremen.de
> Universitaet Bremen/ BCCMS          phone:  +49-(0)421-218-62334
> Am Fallturm 1/ TAB/ Raum 3.12       fax: +49-(0)421-218-62770
> 28359 Bremen  
> 
> PGP: http://www.bccms.uni-bremen.de/cms/people/c_koehler/
> --
> To unsubscribe from this list: send the line "unsubscribe autofs" in

-- 
Dr. rer. nat. Christof Köhler       email: c.koehler@bccms.uni-bremen.de
Universitaet Bremen/ BCCMS          phone:  +49-(0)421-218-62334
Am Fallturm 1/ TAB/ Raum 3.12       fax: +49-(0)421-218-62770
28359 Bremen  

PGP: http://www.bccms.uni-bremen.de/cms/people/c_koehler/
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

  reply	other threads:[~2016-04-11 16:35 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 14:19 autofs reverts to IPv4 for multi-homed IPv6 server ? Christof Koehler
2016-04-08  4:46 ` Ian Kent
2016-04-08 10:10   ` Ian Kent
2016-04-08 10:14     ` Ian Kent
2016-04-08 12:25     ` Christof Koehler
2016-04-08 14:29       ` Christof Koehler
2016-04-08 15:32         ` Christof Koehler
2016-04-10  2:09           ` Ian Kent
2016-04-08 16:12         ` Christof Koehler
2016-04-08 16:15           ` Christof Koehler
2016-04-10  2:17             ` Ian Kent
2016-04-10  2:14           ` Ian Kent
2016-04-09  1:42         ` Ian Kent
2016-04-09  9:56           ` Christof Koehler
2016-04-10  2:29             ` Ian Kent
2016-04-25  4:40             ` Ian Kent
2016-04-25 15:06               ` Christof Koehler
2016-04-26  1:06                 ` Ian Kent
2016-04-26  9:53                   ` Ian Kent
2016-04-26 15:27                     ` Christof Koehler
2016-04-27  1:54                       ` Ian Kent
2016-04-27  2:27                         ` Ian Kent
2016-04-27 16:52                         ` Christof Koehler
2016-04-28  2:56                           ` Ian Kent
2016-04-28  3:21                             ` Ian Kent
2016-04-28  9:12                               ` Christof Koehler
2016-04-28  9:10                             ` Christof Koehler
2016-04-28 10:50                               ` Ian Kent
2016-04-28 11:26                                 ` Christof Koehler
2016-04-28 12:40                                   ` Christof Koehler
2016-04-29  1:54                                   ` Ian Kent
2016-04-29 14:10                                     ` Christof Koehler
2016-04-29 14:42                                       ` Christof Koehler
2016-04-30  3:21                                       ` Ian Kent
2016-04-30 11:36                                         ` Christof Koehler
2016-04-30 15:15                                           ` Christof Koehler
2016-04-30 15:16                                           ` Christof Koehler
2016-05-02  6:01                                           ` Ian Kent
2016-05-02 16:08                                             ` Christof Koehler
2016-05-03  7:58                                               ` Ian Kent
2016-05-03 15:13                                                 ` Christof Koehler
2016-05-04  7:20                                                   ` Ian Kent
2016-05-04 12:38                                                     ` Christof Koehler
2016-04-09  1:35       ` Ian Kent
2016-04-11  2:42     ` Ian Kent
2016-04-11 16:32       ` Christof Koehler
2016-04-11 16:35         ` Christof Koehler [this message]
2016-04-12  1:07           ` Ian Kent
2016-04-08 11:47   ` Christof Koehler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160411163513.GC15079@bccms.uni-bremen.de \
    --to=christof.koehler@bccms.uni-bremen.de \
    --cc=autofs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).