From owner-freebsd-stable@FreeBSD.ORG Sun Jun 25 04:16:15 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 4AF5016A4A6 for ; Sun, 25 Jun 2006 04:16:13 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD1F543D53 for ; Sun, 25 Jun 2006 04:16:12 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 7032B290C25; Sun, 25 Jun 2006 01:16:11 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 98370-02; Sun, 25 Jun 2006 01:16:10 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id C670F290C1E; Sun, 25 Jun 2006 01:16:09 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id C0B7537EC9; Sun, 25 Jun 2006 01:16:09 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id BF7C736622; Sun, 25 Jun 2006 01:16:09 -0300 (ADT) Date: Sun, 25 Jun 2006 01:16:09 -0300 (ADT) From: "Marc G. Fournier" To: Kostik Belousov In-Reply-To: <20060624163845.L1114@ganymede.hub.org> Message-ID: <20060625011227.C1114@ganymede.hub.org> 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> <20060624145432.A1114@ganymede.hub.org> <20060624185203.GC79678@deviant.kiev.zoral.com.ua> <20060624163845.L1114@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Dmitry Morozovsky 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: Sun, 25 Jun 2006 04:16:15 -0000 'k, this has gotta be a leak somewhere ... I'm now up to 6 blocked: 0 8 0 7449224 236552 213 2 1 0 109 0 101 0 475 2890 2143 2 6 92 0 6 0 7481104 247704 578 0 0 0 1196 0 262 0 808 8901 3049 5 16 79 0 6 0 7450820 253576 1385 3 2 3 1379 0 13 0 303 4742 1703 13 13 73 0 6 0 7478168 248372 295 0 0 0 160 0 57 0 428 1900 2616 2 7 92 0 6 0 7473064 249072 1 0 0 0 23 0 6 0 273 822 845 1 2 97 1 6 0 7479000 243164 275 17 7 0 144 0 17 0 317 1572 2180 2 6 92 But there don't appear to be any processes reporting itself as being blocked: pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' 0 30418 30416 6 8 0 4916 2624 ppwait Ds pa 0:00.13 -csh (csh) pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' 0 30418 30416 137 8 0 4916 2624 ppwait Ds pa 0:00.14 -csh (csh) pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' pluto# ps axlww | awk '$10 ~ /^D[^L]/' Or is there something else I should be looking at/for? In the case of this system, its kernel sources from ~May 25th ... On Sat, 24 Jun 2006, Marc G. Fournier wrote: > On Sat, 24 Jun 2006, Kostik Belousov wrote: > >> 2. 2 Giant holders/lockers. Is it constant ? Are the processes >> holding/waiting >> for Giant are the same ? > > Mostly appears to be 'clock' ... > > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.03 [swi4: > clock] > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.03 [swi4: > clock] > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.03 [swi4: > clock] > pluto# ps axlww | grep Giant | grep -v grep > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.03 [swi4: > clock] > pluto# ps axlww | grep Giant | grep -v grep > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.03 [swi4: > clock] > pluto# ps axlww | grep Giant | grep -v grep > pluto# ps axlww | grep Giant | grep -v grep > 0 92517 46540 114 110 0 5032 2412 Giant LV+ p4 0:00.00 -csh > (csh) > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.04 [swi4: > clock] > 1001 14098 1 0 96 0 3308 1324 Giant LsJ ?? 0:04.98 > /usr/local/libexec/postfix/master > pluto# ps axlww | grep Giant | grep -v grep > pluto# ps axlww | grep Giant | grep -v grep > 0 12 0 0 -32 0 0 8 Giant LL ?? 3:07.04 [swi4: > clock] > pluto# ps axlww | grep Giant | grep -v grep > pluto# > > And I suspect that the master is disk i/o, since the iir driver is listed as > still GIANT-LOCKED: > > iir0: mem 0xfc8f0000-0xfc8f3fff irq 30 at > device 9.0 on pci1 > iir0: [GIANT-LOCKED] > >> Ah, and does dmesg show anything ? > > Anything (other then the iir driver) that I'd be looking for in there? Or > could that be what is compounding the problem? Too many things trying to > acquire GIANT over the drive(s), creating a deadlock? Long shot there ... ? > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664