On Fri, 2013-03-08 at 08:55 -0800, Tim Gustafson wrote: > > Right but sticking it in OPTIONS="-O fstype=nfs4" on specific machines > > should work. If it doesn't it's a bug. > > I could have sworn that I tried that before and it didn't work, but I > just tested that now on one of my boxes and it seems to work. That's > good news. > > I still find myself in a bit of a pickle in that some of our NFS > servers are cheap Iomega-brand home NAS boxes that only do NFSv3 and I > need to figure out how to deal with those. I really feel like my best > bet is to start upgrading all the 5.x boxes to 6.x and this whole > problem will just go away. Then, the OS will default to NFSv4 and > fall back to NFSv3 on devices that don't support it. Hahaha, nothing is never simple. There is one other gotcha, and that is older Linux NFS servers only provided NFSv4 global root which can confuse autofs since there's no way to identify the export path corresponding to the global root. The hosts map is most sensitive to that but it also means you can't fall back to NFSv3 for those hosts and clients might not be able to use the same source path between v4 and v3. So you need to check to ensure the servers are sufficiently up to date but that change did happen quite a while ago. Ian -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
