From owner-freebsd-current@FreeBSD.ORG  Thu Sep 29 07:34:10 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 CCEC616A41F;
	Thu, 29 Sep 2005 07:34:10 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7808743D48;
	Thu, 29 Sep 2005 07:34:10 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.48.2])
	by phk.freebsd.dk (Postfix) with ESMTP id 05A81BC6D;
	Thu, 29 Sep 2005 07:34:08 +0000 (UTC)
To: Don Lewis <truckman@FreeBSD.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 29 Sep 2005 00:31:02 PDT."
	<200509290731.j8T7V2OR007019@gw.catspoiler.org> 
Date: Thu, 29 Sep 2005 09:34:08 +0200
Message-ID: <7056.1127979248@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: current@FreeBSD.org
Subject: Re: stress test deadlock involving vm and/or geom 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Thu, 29 Sep 2005 07:34:10 -0000

In message <200509290731.j8T7V2OR007019@gw.catspoiler.org>, Don Lewis writes:

>(kgdb) print runningbufspace
>$3 = 1585152
>(kgdb) print lorunningspace
>$4 = 524288
>print hirunningspace
>$5 = 1048576
>
>so runningbufspace >> hirunningspace
>
>The bufdaemon and the syncer both ignore the runningbufspace limit.
>Maybe they should obey the limit, but each be guaranteed a minimum
>quota.

I'm not quite sure what a/the sensible solution is, but the
lemming-syncer certainly is my prime suspect.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.