With autofs-5.0.4-r3 automount failes to fall-back to ipv4 when nfs server doesnt respond on ipv6. A work-around is to add host with ipv4 address to /etc/hosts, or to go back to autofs-5.0.4-r2 which doesnt have the ipv6 patches that -r3 does. Reproducible: Always Steps to Reproduce: 1. emerge autofs-5.0.4-r3 2. be on an ipv6 networking, make sure nfs server is registered in DNS with ipv6-address 3. configure autofs to mount from the said host 4. see how it failes with "mount(nfs): no hosts available" Actual Results: As mentioned, "mount(nfs): no hosts available" comes in the log, and it fails to automount Expected Results: A fallback to ipv4 when ipv6 fails
nfs doesn't work yet on IPv6 afaik (at least not in mainline kernel)
(In reply to comment #0) > With autofs-5.0.4-r3 automount failes to fall-back to ipv4 when nfs server > doesnt respond on ipv6. A work-around is to add host with ipv4 address to > /etc/hosts, or to go back to autofs-5.0.4-r2 which doesnt have the ipv6 patches > that -r3 does. Could you please test with autofs-5.0.6 which has included a patch regarding IPv6 handling and report whether this issue still persists or has been solved?
(In reply to comment #2) > (In reply to comment #0) > > With autofs-5.0.4-r3 automount failes to fall-back to ipv4 when nfs server > > doesnt respond on ipv6. A work-around is to add host with ipv4 address to > > /etc/hosts, or to go back to autofs-5.0.4-r2 which doesnt have the ipv6 patches > > that -r3 does. > Could you please test with autofs-5.0.6 which has included a patch regarding > IPv6 handling and report whether this issue still persists or has been solved? Please test with the latest version available and re-open this bug if the problem still persists. Thanks.