On Mon, Aug 25, 2008 at 11:41:02AM -0400, Chuck Lever wrote: > Hi Jari- > > On Mon, Aug 25, 2008 at 3:36 AM, Jari Aalto <jari.aalto@xxxxxxxxx> wrote: > > > > Thank you for the NFS howto (last modified 2006). Please add further > > diagnostics to section: > > > > => "I do not have permission to access files on the mounted volume" > > http://nfs.sourceforge.net/nfs-howto/ar01s07.html#pemission_issues > > > > The error condition "Permission denied" also happens in certain NFS > > (client/server) combinations and the workaround is to add additional > > mount parameter at client: > > > > sec=sys > > > > Please add this to the "#pemission_issues" (tag the word seems to have a > > small typo). > > This is a known bug in nfs-utils 1.1.3 when used with older client > kernels that do not support text-based mounts. > > Seems like an esoteric (ie not widespread) problem, but I could easily > be wrong about that. People should be able to upgrade nfs-utils without upgrading their kernel! The referenced debian bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492970 claims the first bad commit is a server-side commit that itself seems to claim to work around a problem? ("For mountd, it does not advertise AUTH_NULL anymore. This is necessary to avoid backward compatibility issue. If AUTH_NULL appears in the list, either the new or the old client will choose that over AUTH_SYS.") Did we ever find the actual root cause? --b. -- 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
