On Jan 18, 2010, at 2:47 PM, Jeff Layton wrote:
With the commit of the statd patches over the weekend, we're now positioned to be able to ship IPv6-enabled nfs-utils in distros. There is a potential snag though... Consider this situation: Admin has a Linux server set up. Server has both IPv4 and IPv6 addrs. Both addresses are in DNS. Without an IPv6-enabled nfs-utils, he mounts via IPv4 and all works fine. Now with an IPv6 enabled nfs-utils, mount.nfs prefers the IPv6 addr and the mount fails (or hangs for a long time and then fails, if it's using NFSv4)...
Why should it fail?
While I don't really like it, I think we may need to consider making mount.nfs prefer IPv4 addrs when it can resolve a hostname to both v4 and v6. Otherwise, we run the risk of breaking an awful lot of working setups...
Isn't that what "proto=udp" vs. "proto=udp6" is for? -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
