From owner-freebsd-current@FreeBSD.ORG  Wed Jan 12 16:54:08 2005
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 9629D16A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 12 Jan 2005 16:54:08 +0000 (GMT)
Received: from web80602.mail.yahoo.com (web80602.mail.yahoo.com
	[66.218.79.91])	by mx1.FreeBSD.org (Postfix) with SMTP id 50AB043D41
	for <freebsd-current@freebsd.org>;
	Wed, 12 Jan 2005 16:54:08 +0000 (GMT)
	(envelope-from mohan_srinivasan@yahoo.com)
Message-ID: <20050112165408.95051.qmail@web80602.mail.yahoo.com>
Received: from [209.79.46.235] by web80602.mail.yahoo.com via HTTP;
	Wed, 12 Jan 2005 08:54:08 PST
Date: Wed, 12 Jan 2005 08:54:08 -0800 (PST)
From: Mohan Srinivasan <mohan_srinivasan@yahoo.com>
To: Daniel Eriksson <daniel_k_eriksson@telia.com>,
	freebsd-current@freebsd.org
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAjFAe51WgFU2M9FDWQ1HRRQEAAAAA@telia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: NFS problems, locking up
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, 12 Jan 2005 16:54:08 -0000

Daniel,

Can you force a core and point me at the core ?

mohan

--- Daniel Eriksson <daniel_k_eriksson@telia.com> wrote:

> 
> I'm still having problems with NFS locking up when moving large amounts of
> data over it on 6-CURRENT from 2005.01.11.05.00.00. This problem has
> persisted for a long time now, and the only thing that seems to cure it is
> running the network stack with giant enabled (debug.mpsafenet=0).
> 
> When it happens, the process doing the copying ends up in "nfsaio" state
> according to ps. Any accesses to the locked mount by other processes ends up
> waiting forever in state "nfs". I have multiple file systems mounted from
> the same server, and only the mount where the data is being moved locks up.
> The others continue to work as expected.
> 
> Server: UP, 6-CURRENT from 2005.01.11.05.00.00, if_vr (POLLING)
> Client: SMP (dual AMD MP), 6-CURRENT from 2005.01.11.05.00.00, if_em
> 
> The machines are connected with a crossover cable. I've tried both
> schedulers (4BSD and ULE) on the client, but it doesn't make any difference
> (server is running 4BSD). PREEMPTION is enabled on both server and client.
> ADAPTIVE_GIANT is enabled on the client.
> 
> /Daniel Eriksson
> 
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>