From owner-freebsd-current@FreeBSD.ORG  Thu Jul 28 11:53:01 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 F161816A41F;
	Thu, 28 Jul 2005 11:53:01 +0000 (GMT)
	(envelope-from keramida@freebsd.org)
Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 110B443D46;
	Thu, 28 Jul 2005 11:53:00 +0000 (GMT)
	(envelope-from keramida@freebsd.org)
Received: from beatrix.daedalusnetworks.priv (aris.bedc.ondsl.gr
	[62.103.39.226])
	by aiolos.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id
	j6SBqqZZ003017; Thu, 28 Jul 2005 14:52:53 +0300
Received: from beatrix.daedalusnetworks.priv (localhost [127.0.0.1])
	by beatrix.daedalusnetworks.priv (8.13.3+Sun/8.13.3) with ESMTP id
	j6SBqqiY020381; Thu, 28 Jul 2005 14:52:52 +0300 (EEST)
Received: (from keramida@localhost)
	by beatrix.daedalusnetworks.priv (8.13.3+Sun/8.13.3/Submit) id
	j6SBqpIC020380; Thu, 28 Jul 2005 14:52:51 +0300 (EEST)
Date: Thu, 28 Jul 2005 14:52:51 +0300
From: Giorgos Keramidas <keramida@freebsd.org>
To: Julian Elischer <julian@elischer.org>
Message-ID: <20050728115251.GA20091@beatrix.daedalusnetworks.priv>
References: <42E88135.30603@elischer.org> <42E88F2B.5000108@elischer.org>
	<20050728082844.GW46538@darkness.comp.waw.pl>
	<42E898A6.6010803@elischer.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42E898A6.6010803@elischer.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
	Pawel Jakub Dawidek <pjd@freebsd.org>
Subject: Re: VFS/VM over-runs. Was: Apparent strange disk behaviour in 6.0
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, 28 Jul 2005 11:53:02 -0000

On 2005-07-28 01:34, Julian Elischer <julian@elischer.org> wrote:
> I wonder if there is some tunable that can be changed? or whether it's
> just a bug..
>
> I think that a write that finds no buffer space should first free old
> unused buffers, and if there aren't any it should just wait.  Where's
> alan when you need him :-)

Setting vm.swap_idle_enabled to 0 seemed to help when I observed similar
problems in the past.  I thought this was fixed months ago though.  It
may be a false impression I got by forgetting to re-enable it and check
that this was indeed fixed.