Package: autofs
Version: 5.0.7-3
Severity: important
Tags: ipv6
Current setup:
% host amys.codelibre.net
amys.codelibre.net has IPv6 address 2001:8b0:860:ddbd:3aea:a7ff:feab:6153
% cat /etc/auto.nfs
amys -fstype=nfs4 amys.codelibre.net:/
% cat /etc/auto.master
/nfs /etc/auto.nfs
% ls /nfs/amys/
ls: reading directory /nfs/amys/: Input/output error
Feb 4 21:48:59 ravenclaw automount[5931]: handle_packet: type = 3
Feb 4 21:48:59 ravenclaw automount[5931]: handle_packet_missing_indirect:
token 13, name amys, request pid 5967
Feb 4 21:48:59 ravenclaw automount[5931]: attempting to mount entry /nfs/amys
Feb 4 21:48:59 ravenclaw automount[5931]: lookup_mount: lookup(file): looking
up amys
Feb 4 21:48:59 ravenclaw automount[5931]: lookup_mount: lookup(file): amys ->
-fstype=nfs4,rw,hard,intr amys.codelibre.net:/
Feb 4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): expanded
entry: -fstype=nfs4,rw,hard,intr amys.codelibre.net:/
Feb 4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): gathered
options: fstype=nfs4,rw,hard,intr
Feb 4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun):
dequote("amys.codelibre.net:/") -> amys.codelibre.net:/
Feb 4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): core of
entry: options=fstype=nfs4,rw,hard,intr, loc=amys.codelibre.net:/
Feb 4 21:48:59 ravenclaw automount[5931]: sun_mount: parse(sun): mounting root
/nfs, mountpoint amys, what amys.codelibre.net:/, fstype nfs4, options
rw,hard,intr
Feb 4 21:48:59 ravenclaw automount[5931]: mount_mount: mount(nfs): root=/nfs
name=amys what=amys.codelibre.net:/, fstype=nfs4, options=rw,hard,intr
Feb 4 21:48:59 ravenclaw automount[5931]: mount_mount: mount(nfs): nfs
options="rw,hard,intr", nobind=0, nosymlink=0, ro=0
Feb 4 21:49:00 ravenclaw automount[5931]: mount(nfs): no hosts available
Feb 4 21:49:00 ravenclaw automount[5931]: dev_ioctl_send_fail: token = 13
Feb 4 21:49:00 ravenclaw automount[5931]: failed to mount /nfs/amys
The NFS setup does work mounting by hand, so the server and client /can/ work.
In this example, the server is FreeBSD 10.0-RELEASE exporting a set of ZFS
datasets.
# mount -t nfs4 amys.codelibre.net:/home /home
findmnt -lu | grep /home
/home amys.codelibre.net:/home nfs4
rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=2001:8b0:860:ddbd:62a4:4cff:fe5f:1257,local_lock=none,addr=2001:8b0:860:ddbd:3aea:a7ff:feab:6153
/home/rleigh amys.codelibre.net:/home/rleigh nfs4
rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=2001:8b0:860:ddbd:62a4:4cff:fe5f:1257,local_lock=none,addr=2001:8b0:860:ddbd:3aea:a7ff:feab:6153
If I change the /etc/auto.nfs map to:
amys -fstype=nfs4 amys.lan:/
then the mount /does/ work. This is because it's using the IPv4
DHCP name and address. It doesn't work fully (the mount is
exported to a restricted set of IPv6 hosts only), intentionally,
but autofs does its part of the job correctly despite this.
It looks like this is down to autofs not handling names using only
IPv6 addresses. Not sure why this happens given that I would have
expected it to just pass this directly to mount(8) but it's
presumably doing more than that. Not sure exactly what the cause
is, though /usr/lib/x86_64-linux-gnu/autofs/mount_nfs.so is using
getaddrinfo and I can't see any obvious defect with a quick glance
over the sources.
Regards,
Roger
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (550, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages autofs depends on:
ii libc6 2.17-97
ii libxml2 2.9.1+dfsg1-3
ii multiarch-support 2.17-97
ii ucf 3.0027+nmu1
Versions of packages autofs recommends:
ii kmod 16-2
ii module-init-tools 16-2
ii nfs-common 1:1.2.8-5
autofs suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
