On Tue, Mar 03, 2009 at 12:04:17PM +0200, Benny Halevy wrote: > On Sep. 29, 2008, 20:26 +0300, "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote: > > > > (Maybe you built a new kernel with nfsd built-in instead of built as a > > module?) > > > > But I thought nfs-utils was supposed to fall back on old behavior when > > the nfsd filesystem wasn't found. > > Doesn't seem so. Right. The old behavior depends on mountd telling the server about each client as it mounts, and that isn't adequate in some cases: for example, since nfsv4 clients never talk directly to mountd at all (they first call nfsd directly), they need to be able to call up to mountd to ask about each client as it arrives, and the old interface doesn't provide a mechanism to do that. But in this case I don't see any reason the old interface shouldn't be good enough. > Steve: any chance this bug is fixed anywhere? It shouldn't be hard to fix. If someone has the time to work on it but doesn't know the code, just testing with varied versions of nfs-utils and the kernel would help determine whether the problem is in mountd or in the kernel, and when it was introduced. --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
