From owner-freebsd-stable@FreeBSD.ORG Sat Jun 24 11:43:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97AD516A4CA for ; Sat, 24 Jun 2006 11:43:01 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 988D643D53 for ; Sat, 24 Jun 2006 11:43:00 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.6) with ESMTP id k5OBgwco037142; Sat, 24 Jun 2006 15:42:59 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 24 Jun 2006 15:42:58 +0400 (MSD) From: Dmitry Morozovsky To: Kostik Belousov In-Reply-To: <20060624090656.GB79678@deviant.kiev.zoral.com.ua> Message-ID: <20060624154017.E30039@woozle.rinet.ru> References: <20060623172557.H1114@ganymede.hub.org> <261AD16B-C3FE-4671-996E-563053508CE8@mac.com> <20060624022227.X1114@ganymede.hub.org> <20060624115505.E14669@woozle.rinet.ru> <20060624090656.GB79678@deviant.kiev.zoral.com.ua> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sat, 24 Jun 2006 15:42:59 +0400 (MSD) Cc: freebsd-stable@freebsd.org Subject: Re: vmstat 'b' (disk busy?) field keeps climbing ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2006 11:43:01 -0000 On Sat, 24 Jun 2006, Kostik Belousov wrote: KB> > MGF> > 'b' stands for "blocked", not "busy". Judging by your page fault rate KB> > MGF> > and the high number of frees and pages being scanned, you're probably KB> > MGF> > swapping tasks in and out and are waiting on disk. Take a look at KB> > MGF> > "vmstat -s", and consider adding more RAM if this is correct... KB> > MGF> KB> > MGF> is there a way of finding out what processes are blocked? KB> > KB> > Aren't they in 'D' status by ps? KB> Use ps axlww. In this way, at least actual blocking points are shown. /me knows ;-) OTOH, I'm faurly sure scrappy@ should know this very well... Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------