On Tue, Sep 30, 2008 at 09:51:08PM +0800, howard chen wrote: > Hello, > > On Tue, Sep 30, 2008 at 1:26 AM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > It looks like nfsd is supposed to be mounted on load of the nfsd module, > > by a line in /etc/modprobe.d/modprobe.conf. > > > > (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. > > > Are there any related docs I should read? The "exportfs" man page explains a little about the "legacy" vs "new" modes of mountd/exportfs operation. > As mentioned before, the server was working before the reboot, really > don't understand why it behave in this way...Need to find out the > reason. As I said, two things happened: 1. The "nfsd" filesystem didn't get mounted under /proc/ as it's suppose to be. 2. The server therefore should have been using the "legacy" mode of operation. But it didn't work for some reason. I'm not sure in either case. If you do put an explicit nfsd mount in the fstab, then you won't see this problem again. --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
