Date: Thu, 26 May 2005 07:49:53 -0500 (CDT) From: "Viren Patel" <virenp@mail.utexas.edu> To: "Kris Kennaway" <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: Re: NFS broken after upgrading to 5.4 Message-ID: <1144.66.25.129.27.1117111793.squirrel@mail.cm.utexas.edu> In-Reply-To: <20050526014526.GA7378@xor.obsecurity.org> References: <1282.66.25.129.27.1117067480.squirrel@mail.cm.utexas.edu> <20050526010713.GA92954@xor.obsecurity.org> <1475.66.25.129.27.1117071597.squirrel@mail.cm.utexas.edu> <20050526014526.GA7378@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > What does ^T show for the status of the 'hung' process? > Are you > certain that DNS resolution is working correctly on both > machines? > > Kris > > Thanks for your help. Interestingly when I tried the mounts this morning they all worked, so I can't provide ^T output. Go figure. Since my clients and the server are communicating over a private LAN, they don't use DNS. However /etc/nsswitch.conf contains: hosts: files dns and in /etc/hosts I have: 127.0.0.1 localhost 192.168.0.10 backuphost The problem occurred whether I used IP or hostname. I've also noticed that mount_nfs tended to succeed if preceded by a ping to the backuphost. I rebooted a client and tried mounting without ping and it worked just fine. It's all behaving really flakily. Basically it amounts to sometimes it works and sometimes it doesn't and there doesn't seem to be a pattern. Viren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1144.66.25.129.27.1117111793.squirrel>