From owner-freebsd-current@FreeBSD.ORG  Wed Aug 27 13:04:51 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2D1FD16A4BF; Wed, 27 Aug 2003 13:04:51 -0700 (PDT)
Received: from mx1.tekgenesis.net (server1.cluster1.tekgenesis.net
	[64.235.250.21])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6E84F43FDF; Wed, 27 Aug 2003 13:04:50 -0700 (PDT)
	(envelope-from wiz@mx1.tekgenesis.net)
Received: by mx1.tekgenesis.net (Postfix, from userid 1000)
	id 557C4B81C; Wed, 27 Aug 2003 10:04:50 -1000 (HST)
Date: Wed, 27 Aug 2003 10:04:50 -1000
From: Jason Dambrosio <jason@wiz.cx>
To: Robert Watson <rwatson@freebsd.org>
Message-ID: <20030827200450.GA29767@tekgenesis.net>
References: <3F4BEA15.3030104@telia.com>
	<Pine.NEB.3.96L.1030827090202.23748B-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.NEB.3.96L.1030827090202.23748B-100000@fledge.watson.org>
User-Agent: Mutt/1.4i
cc: current@freebsd.org
Subject: Re: nfs tranfers hang in state getblck or nfsread
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Aug 2003 20:04:51 -0000

On Wed, Aug 27, 2003 at 09:06:41AM -0400, Robert Watson wrote:
> I have a very similar configuration, but it sounds like I'm not bumping
> into the same problem.  Are you using NFSv2 or v3, and how many file
> systems are you mounting?  Are you generally using UFS1 or UFS2?  Right
> now, I'm mounting a single UFS2 file system was the root, and I believe
> right now we always mount NFS roots at NFSv2, which could by why I'm not
> seeing the same problem...

    I had the same problem, replacing nfsv3 with tcp in my fstab fixed it.

    4.8 server (ufs1), 5.0/5.1 clients, fstab looks like this now:

main:/data/home /data/home nfs rw,tcp,soft,intr,bg,rdirplus,noatime,nosuid,nodev
main:/data/config /data/config nfs rw,tcp,soft,intr,bg,rdirplus,noatime,nosuid,nodev
main:/data/www /data/www nfs rw,tcp,soft,intr,bg,rdirplus,noatime,nosuid,nodev

Jason