From owner-freebsd-questions@FreeBSD.ORG Thu May 26 12:49:54 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B16616A41C for ; Thu, 26 May 2005 12:49:54 +0000 (GMT) (envelope-from virenp@mail.utexas.edu) Received: from smtp.cm.utexas.edu (smtp.cm.utexas.edu [146.6.135.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id C44A943D1D for ; Thu, 26 May 2005 12:49:53 +0000 (GMT) (envelope-from virenp@mail.utexas.edu) Received: from mail.cm.utexas.edu (smtp.cm.utexas.edu [146.6.135.3]) by smtp.cm.utexas.edu (Postfix) with ESMTP id 62FC06D484; Thu, 26 May 2005 07:49:53 -0500 (CDT) Received: from 66.25.129.27 (SquirrelMail authenticated user vpatel) by mail.cm.utexas.edu with HTTP; Thu, 26 May 2005 07:49:53 -0500 (CDT) 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> Date: Thu, 26 May 2005 07:49:53 -0500 (CDT) From: "Viren Patel" To: "Kris Kennaway" User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-questions@freebsd.org Subject: Re: NFS broken after upgrading to 5.4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: virenp@mail.utexas.edu List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2005 12:49:54 -0000 > > 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