Date: Fri, 12 Oct 2007 09:42:38 -0600 From: James <jamesh@lanl.gov> To: Michael Smith <mksmith@adhost.com> Cc: questions@freebsd.org Subject: Re: Questions about HUP'ing nfsd Message-ID: <1192203758.33933.69.camel@secretariat.lanl.gov> In-Reply-To: <2BBC6552-76B0-4D22-9F68-BEC9E46C0FFB@adhost.com> References: <2BBC6552-76B0-4D22-9F68-BEC9E46C0FFB@adhost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2007-10-12 at 08:25 -0700, Michael Smith wrote: > Hello All: > > We have a NAS that's running 6.2 with nfds, mountd, rpc_statd, > rpcbind and rpc_lockd. Last night we had a scenario where nfs > clients, once disconnected, couldn't reconnect to the NAS, reporting > RPC timeouts. > I've had RPC timeouts before. Turned out my NFS was misconfigured - I had a weird flag in /etc/rc.conf that was preventing mountd from loading. Could be someone made an undocumented change - you may want to check it. > My question is, in troubleshooting this sort of thing, is there a > proper sequence for stopping and restarting the various services > associated with nfs? Any hints would be greatly appreciated. > Linux usually likes an exportfs -r, service portmap restart, service nfs restart. I've usually gone for a similar thing in FreeBSD. Something like: /etc/rc.d/mountd onereload /etc/rc.d/nfs restart I think that does it all. Otherwise, there's always shutdown NOW and then a ctrl-d. If you're not sshing in, of course. James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1192203758.33933.69.camel>