From owner-freebsd-questions@FreeBSD.ORG Thu May 26 01:39:58 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 37FED16A41C for ; Thu, 26 May 2005 01:39:58 +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 F198643D1D for ; Thu, 26 May 2005 01:39:57 +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 8CA2A6D47F; Wed, 25 May 2005 20:39:57 -0500 (CDT) Received: from 66.25.129.27 (SquirrelMail authenticated user vpatel) by mail.cm.utexas.edu with HTTP; Wed, 25 May 2005 20:39:57 -0500 (CDT) Message-ID: <1475.66.25.129.27.1117071597.squirrel@mail.cm.utexas.edu> In-Reply-To: <20050526010713.GA92954@xor.obsecurity.org> References: <1282.66.25.129.27.1117067480.squirrel@mail.cm.utexas.edu> <20050526010713.GA92954@xor.obsecurity.org> Date: Wed, 25 May 2005 20:39:57 -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 01:39:58 -0000 > On Wed, May 25, 2005 at 07:31:20PM -0500, Viren Patel > wrote: >> Hello all. I have several FreeBSD clients connecting to >> a >> FreeBSD NFS server via a private gigabit LAN for backup >> purposes. Both clients and server has IPFW with all >> traffic between clients and server allowed on the >> private >> LAN. All clients and the server were running >> 5.3-RELEASE-p10 with IPFW, and NFS was working just >> fine. >> Then I upgraded all clients to 5.4-RELEASE-p1 and the >> NFS >> was working fine. Finally I upgraded the NFS server to >> 5.4-RELEASE-p1 and now NFS has stopped working. The >> clients experience RPC timeouts: >> >> RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out >> >> My NFS server rc.conf has the following as per manual: >> >> nfs_server_enable="YES" >> rpcbind_enable="YES" >> mountd_flags="-r" >> >> Clients have: >> >> nfs_client_enable="YES" >> >> IPFW rules amount to: >> >> allow all from NFS_SERVER to NFS_CLIENT in via >> INTERNAL_IF >> allow all from NFS_CLIENT to NFS_SERVER out via >> INTERNAL_IF >> >> and appear at the top of the ruleset. > > Double check this, then triple-check it, because a local > configuration > difference like this is likely to be your cause. > >> Obviously something has changed in the NFS system under >> 5.4 > > Not that I can think of. > > Kris > I have checked my configuration multiple times. Nothing there has changed between 5.3 and 5.4. I have even disabled the firewalls on both clients and server but the same problem is present. Another interesting behavior: upon reboot, mount_nfs occasionally succeeds. However if I then go to another client and try to access the NFS server it doesn't work. If I then go back to the first client and try to unmount the NFS partition it also hangs. Viren