Date: Mon, 19 Apr 2010 12:48:39 -0400 From: peter@vfemail.net To: freebsd-questions@freebsd.org Subject: Re: Request for mount_nfs assistance Message-ID: <20100419165048.B6F6C106567C@hub.freebsd.org> In-Reply-To: <y2w6f8779041004190900v58366413laa3cc1dc36df0358@mail.gmail .com> References: <20100419152330.42C931065674@hub.freebsd.org> <y2w6f8779041004190900v58366413laa3cc1dc36df0358@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
192.168.0.244's /etc/exports file says: /usr/home1 -maproot=root 192.168.0.252 /usr/home1 -maproot=root 192.168.0.253 192.168.0.252 is the machine that should have access to 192.168.0.244's drive, but was having difficulty obtaining it. I'm kind of surprised to see the entry for 192.168.0.253, because I don't think that machine has any need for access to the drive. Do these two entires in the /etc/exports file create a conflict? I don't believe there were any recent network-related changes. ------- At 12:00 PM 4/19/2010, Jon Mercer wrote: >What information is contained in the /etc/exports file on the NFS server? If >that changed between NFS Server restarts that _could_ be the cause. > >Also, has there been any simultaneous change in the network across which the >servers speak? Especially with regard to port 111. > > > >On 19 April 2010 15:38, <peter@vfemail.net> wrote: > >> >> I have two servers funning FreeBSD. For the past four years, an: >> >> /sbin/mount_nfs 192.168.0.244:/usr/home1 /home1 >> >> command has successfully allowed one server access to data on the other >> server's hard drive. >> >> This morning, following reboots of both servers, the mount_nsf command >> fails, returns: >> >> 192.168.0.244:/usr/home1: RPCPROG_MNT: RPC: Timed out >> >> error messages. >> >> Each server can ping the other and connect via ssh; the hardware's working >> fine; I don't believe anything's changed on either server recently; and the >> find command doesn't indicate that any system files have been altered in the >> past week. >> >> I'm at a complete loss for any explanation of the failure, and I'm >> uncertain how to diagnose and fix the problem. >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscribe@freebsd.org" >> > > > >-- >----------------------------------------------------------------------- >Jon Mercer Director Achean Limited > > http://www.achean.com > http://uk.linkedin.com/in/jonmercer >----------------------------------------------------------------------- >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100419165048.B6F6C106567C>