On Tue, 2018-07-31 at 17:09 -0500, Patrick Goetz wrote:
> I have a very simple automounter configuration on an Ubuntu 18.04 client
> machine:
What is in your autofs.conf and what is in your nfsmount.conf?
>
> root@viper:/etc# cat auto.master
>
> /home /etc/auto.home
>
>
> root@viper:/etc# cat auto.home
>
> * snakeskin:/home/&
>
>
> This was all working fine with an Ubuntu 16.04.4 server, as well as an
> identically configured Ubuntu 18.04 server.
>
> After a recent system upgrade to the NFS server to Ubuntu 16.04.5, the
> automounter stopped mounting home directories. Running
>
> # automount -f -v --debug
>
> the output looks like:
>
> ====================================
> root@viper:/etc# automount -v -f --debug
> Starting automounter version 5.1.2, master map /etc/auto.master
> using kernel protocol version 5.02
> lookup_nss_read_master: reading master file /etc/auto.master
> do_init: parse(sun): init gathered global options: (null)
> lookup_read_master: lookup(file): read entry /home
> master_do_mount: mounting /home
> automount_path_to_fifo: fifo name /var/run/autofs.fifo-home
> lookup_nss_read_map: reading map file /etc/auto.home
> do_init: parse(sun): init gathered global options: (null)
> mounted indirect on /home with timeout 300, freq 75 seconds
> st_ready: st_ready(): state = 0 path /home
> handle_packet: type = 3
> handle_packet_missing_indirect: token 273, name pgoetz, request pid 4246
> attempting to mount entry /home/pgoetz
> lookup_mount: lookup(file): looking up pgoetz
> lookup_mount: lookup(file): pgoetz -> snakeskin:/home/&
> parse_mount: parse(sun): expanded entry: snakeskin:/home/pgoetz
> parse_mount: parse(sun): gathered options:
> parse_mount: parse(sun): dequote("snakeskin:/home/pgoetz") ->
> snakeskin:/home/pgoetz
> parse_mount: parse(sun): core of entry: options=, loc=snakeskin:/home/pgoetz
> sun_mount: parse(sun): mounting root /home, mountpoint pgoetz, what
> snakeskin:/home/pgoetz, fstype nfs, options (null)
> mount_mount: mount(nfs): root=/home name=pgoetz
> what=snakeskin:/home/pgoetz, fstype=nfs, options=(null)
> get_nfs_info: called with host snakeskin(128.83.133.19) proto 6 version 0x30
> get_nfs_info: called with host snakeskin(128.83.133.19) proto 17 version
> 0x30
> mount(nfs): no hosts available
> dev_ioctl_send_fail: token = 273
> failed to mount /home/pgoetz
> st_readmap: state 1 path /home
> re-reading map for /home
> lookup_nss_read_map: reading map file /etc/auto.home
> do_init: parse(sun): init gathered global options: (null)
> handle_packet: type = 3
> st_ready: st_ready(): state = 4 path /home
> handle_packet_missing_indirect: token 274, name pgoetz, request pid 4246
> attempting to mount entry /home/pgoetz
> lookup_mount: lookup(file): looking up pgoetz
> lookup_mount: lookup(file): pgoetz -> snakeskin:/home/&
> parse_mount: parse(sun): expanded entry: snakeskin:/home/pgoetz
> parse_mount: parse(sun): gathered options:
> parse_mount: parse(sun): dequote("snakeskin:/home/pgoetz") ->
> snakeskin:/home/pgoetz
> parse_mount: parse(sun): core of entry: options=, loc=snakeskin:/home/pgoetz
> sun_mount: parse(sun): mounting root /home, mountpoint pgoetz, what
> snakeskin:/home/pgoetz, fstype nfs, options (null)
> mount_mount: mount(nfs): root=/home name=pgoetz
> what=snakeskin:/home/pgoetz, fstype=nfs, options=(null)
> get_nfs_info: called with host snakeskin(128.83.133.19) proto 6 version 0x30
> get_nfs_info: called with host snakeskin(128.83.133.19) proto 17 version
> 0x30
> mount(nfs): no hosts available
> dev_ioctl_send_fail: token = 274
> failed to mount /home/pgoetz
> =============================================
>
> As far as I can tell, switching back and forth between the working
> Ubuntu 18.04 NFS server and the not-working Ubuntu 16.04.5 NFS server,
> automount is clearly mounting the home directories using NFS v3, even
> though I thought I had explicitly disabled this in:
>
> /etc/default/nfs-kernel-server
>
> RPCNFSDARGS="-N 2 -N 3 -U"
>
>
> My working hypothesis is that Ubuntu 18.04 is ignoring this (based on
> the debug output it is clearly allowing NFS v3 mounts via the
> automounter), and 16.04.4 did as well (not tested, as it just worked),
> but something changed in 16.04.5 where they are now prohibiting NFS v3
> mounts, as I requested.
>
>
> I fail to see why NFS v3 is still being used, given that NFS v4 has been
> out for over a decade. How can I get autofs to use NFS v4?
>
> --
> To unsubscribe from this list: send the line "unsubscribe autofs" in
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
