On 04/09/2015 12:34 PM, Gregory Boyce wrote: > Folks, > > I've been encountering a problem with NFS clients attempting to mount > from a netapp via UDP where the netapp is responding on the wrong > interface. On some of our older systems, this mount worked properly, > while on newer systems nfs-utils ends up failing the mount. Mounting > via TCP works fine. > > It appears that there has been various related discussions over the > years, and a relevant Redhat bug opened back in 2006: > > http://article.gmane.org/gmane.linux.nfs/22778/match=connect+udp > https://bugzilla.redhat.com/show_bug.cgi?id=208244 > > Is there a general recommendation for people in this sort of > situation? I'm assuming the code is currently using connected UDP > sockets (I'm more of a sysadmin than a developer). Is there an option > I'm missing to disable this? Otherwise does anyone know of a patch to > change the behavior? I have some patches that allow binding an NFS client to a particular local IP. You need modified mount.nfs tools as well. These patches might fix your problem, but I am not certain about that. My kernel trees have various other patches as well...you can pick out just the NFS stuff if you care to. Otherwise, the kernel should generally build, install, and work the same as upstream kernels. https://github.com/greearb/nfs-utils-ct # This one has cleaner patch set, but not much testing. http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.19.dev.y/.git;a=summary # This is lots of extraneous wifi patches, but has had good testing, # including the nfs bind-to-local-IP feature. http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=summary Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.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
