From owner-freebsd-stable@FreeBSD.ORG  Wed Nov 22 15:29:49 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@FreeBSD.ORG
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 89D7916A403
	for <freebsd-stable@FreeBSD.ORG>; Wed, 22 Nov 2006 15:29:49 +0000 (UTC)
	(envelope-from scsprong@gmail.com)
Received: from volte.student.utwente.nl (volte.student.utwente.nl
	[130.89.162.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E152B43D72
	for <freebsd-stable@FreeBSD.ORG>; Wed, 22 Nov 2006 15:29:19 +0000 (GMT)
	(envelope-from scsprong@gmail.com)
Received: from www.private (mail.private [10.10.10.1])
	by volte.student.utwente.nl (Postfix) with ESMTP id 85A24EBCF6
	for <freebsd-stable@FreeBSD.ORG>; Wed, 22 Nov 2006 16:29:47 +0100 (CET)
Date: Wed, 22 Nov 2006 16:29:47 +0100 (CET)
From: "S.C.Sprong" <scsprong@gmail.com>
To: freebsd-stable@FreeBSD.ORG
Message-ID: <20061122162646.F1354@volte.student.utwente.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: Re: Trouble: NFS via TCP
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "S.C.Sprong" <scsprong@gmail.com>
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2006 15:29:49 -0000

From: "S.C.Sprong" <scsprong@gmail.com>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Trouble: NFS via TCP
In-Reply-To: <200611091717.kA9HH631005085@lurza.secnetix.de>
X-Newsgroups: mpc.lists.freebsd.stable,muc.lists.freebsd.stable

In article <200611091717.kA9HH631005085@lurza.secnetix.de> you wrote:
>Symptom:  As soon as I use the -T option (TCP) with the mount command,
>it simply hangs forever.  If I use the intr/soft flags, I can Ctrl-C
>it after a while, and the mount indeed appears in the output from
>"mount", but any command that tries to access it (e.g. ls(1)) also
>hangs. Even umount(8) hangs.

I've had the same problems and made similar observations.
A few more:

- Running 'tcpdump tcp port 2048' on the NFS server _after_ the client
  is stuck in this state causes a spontaneous reboot of the server.

- Running 'netstat -a' shows that the client is stuck in an endless
  connect-disconnect loop and chews through port numbers.

- It happens with fxp, rl, and sis cards.

- TCP initial window size advertisement doesn't seem to matter.

- While using UDP I may have encountered a similar bus as described
  in NetBSD bugs bin/20663: deadlock in cron(8)


Many reboots later, I solved my problem by disabling the following tweaks
I had in /etc/sysctl.conf for ages:

#vfs.nfs.bufpackets=8
# 20050510: read 16 blocks instead of 8
#vfs.read_max=16
# 20060908: obsolete?
#vfs.nfsrv.gatherdelay_v3=10000

And reverted to the system defaults:

vfs.nfs4.nfsv3_commit_on_close: 0
vfs.nfs.bufpackets: 4
vfs.nfs.nfs_ip_paranoia: 1
vfs.nfs.nfs_directio_allow_mmap: 1
vfs.nfs.nfs_directio_enable: 0
vfs.nfs.clean_pages_on_close: 1
vfs.nfs.nfsv3_commit_on_close: 0
vfs.nfs.access_cache_timeout: 2
vfs.nfsrv.nfs_privport: 1
vfs.nfsrv.commit_miss: 0
vfs.nfsrv.commit_blks: 0
vfs.nfsrv.async: 0
vfs.nfsrv.gatherdelay_v3: 0
vfs.nfsrv.gatherdelay: 10000

Hope this helps,
scs