On Mon, Feb 07, 2011 at 04:59:35PM -0500, J. Bruce Fields wrote: > > Changes to /etc/exports aren't automatically detected, so you need a > server restart or an exportfs -ra after any change. Yep: exportfs -au # unload old rules exportfs # verify it is empty exportfs -a # load it up exportfs # verify it loaded So I would have expected it to have reloaded. > > OK, so maybe the problem was just that mountd never found out about your > original /etc/exports file? That wouldn't explain why it has stopped working now. Neither the exportfs commands above nor a service nfs stop/start yields a working mount from the client. Restarting nfsd with an export of: [root@adept internal.excfb.com]# exportfs /fooper 192.168.2.0/255.255.255.0 [root@adept internal.excfb.com]# uname -a Linux adept.internal.excfb.com 2.6.34.7-66.fc13.i686.PAE #1 SMP Wed Dec 15 07:21:49 UTC 2010 i686 i686 i386 GNU/Linux Does yield a mount. > > --b. > -- Tom Haynes ex-cfb -- 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
