Date: Wed, 12 Nov 2008 17:20:09 -0800 From: Ted Faber <faber@isi.edu> To: Derek Taylor <det135@psu.edu>, freebsd-current@freebsd.org, dfr@freebsd.org Subject: Re: problems with nfsd (due to RPCSEC_GSS changes?) Message-ID: <20081113012009.GA2904@zod.isi.edu> In-Reply-To: <20081113001804.GA10822@insightsol.com> References: <d04e16b70811111730w1bb7766ei4a628f2d8ddd9078@mail.gmail.com> <20081112150850.GC34909@psu.edu> <20081113001804.GA10822@insightsol.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wed, Nov 12, 2008 at 04:18:04PM -0800, Navdeep Parhar wrote: > On Wed, Nov 12, 2008 at 10:08:50AM -0500, Derek Taylor wrote: > > On Tue, 11 Nov 2008, Navdeep Parhar wrote: > > >Ultimately, I had to add NFS_LEGACYRPC in order to get a working nfsd. > > >Looks like there may be a problem with the new code that was added as > > >part of RPCSEC_GSS support. Note that I did not enable KGSSAPI in my > > >kernel as I have no need for it. > > > > It sounds like you were bitten by the behavior documented in paragraph > > two of the commit log: > > The NFS code currently contains support for both the new RPC > > implementation and the older legacy implementation inherited > > from the original NFS codebase. The default is to use the new > > implementation - add the NFS_LEGACYRPC option to fall back to > > the old code. When I merge this support back to RELENG_7, I > > will probably change this so that users have to 'opt in' to > > get the new code. > > My reading of the commit log was that the new code would work out of > the box, and that NFS_LEGACYRPC was for unforeseen problems (just like > the one I ran into). I expected the new RPC implementation to work > without any change to kernel conf or anything else. > > I don't feel any expected brokenness was documented in that paragraph. For what it's worth, I made a similar transition and the new RPC code paniced my NFS client. At least, I believe that was the cause as the panic has been removed by reverting back to the old RPC code. I think this is probably worth a HEADS UP or an entry in UPDATING. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkbgMgACgkQaUz3f+Zf+XuYBgCgrkwLgl6jNyoJwRgBSHnZeLS2 P3MAoPowwsGOqgnn18r5q8Fz09iaKrFp =qiZT -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081113012009.GA2904>