From owner-freebsd-current@FreeBSD.ORG  Mon Jan 12 14:29:55 2004
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 40C7116A4CE
	for <current@FreeBSD.org>; Mon, 12 Jan 2004 14:29:55 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EF81643D2D
	for <current@FreeBSD.org>; Mon, 12 Jan 2004 14:29:53 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0CMTb7E034275;
	Mon, 12 Jan 2004 14:29:41 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200401122229.i0CMTb7E034275@gw.catspoiler.org>
Date: Mon, 12 Jan 2004 14:29:37 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: dwhite@gumbysoft.com
In-Reply-To: <20040112141254.V54897@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: mi@aldan.algebra.com
cc: current@FreeBSD.org
Subject: Re: core-dumping over NFS
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: Mon, 12 Jan 2004 22:29:55 -0000

On 12 Jan, Doug White wrote:
> On Mon, 12 Jan 2004, Don Lewis wrote:
> 
>> On 12 Jan, Mikhail Teterin wrote:
>>
>> > 	. 5.2-CURRENT (Dec 14) server, RedHat-9 client:
>> > 		core is created properly, but sometimes the server goes
>> > 		into a frenzy with the sys-component (bufdaemon) taking
>> > 		up the entire 100% of the CPU-time (P4 at 2GHz); it only
>> > 		writes @4Mb/s (~14% of the disk's bandwidth) and the
>> > 		only cure is to restart the /etc/rc.d/nfsd; trying to,
>> > 		for example, switch from X11 to a textual console, when
>> > 		this is happening reliably hangs the machine.
>>
>> I saw something similar a in the last month when running iozone on a
>> FreeBSD client with an nfs file system mounted from a FreeBSD server.  I
>> think this was in the 5.2-BETA timeframe.  The client typically ran out
>> of CPU first, but the server was not far behind.  This happened in the
>> tests with the larger file and/or block sizes.  Bufdaemon was typically
>> the big consumer of CPU.
> 
> Hm, I can attempt to reproduce this on 5.2-rel or -current. Can you
> provide the options used to iozone?

I think I used the defaults other than cranking up the max file size go
1GB to match the memory size on my server.  It took a long time to run
the full set of tests ...