Date: Sat, 24 Jun 2006 16:42:45 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org, Dmitry Morozovsky <marck@rinet.ru> Subject: Re: vmstat 'b' (disk busy?) field keeps climbing ... Message-ID: <20060624163845.L1114@ganymede.hub.org> In-Reply-To: <20060624185203.GC79678@deviant.kiev.zoral.com.ua> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Intel Integrated RAID Controller> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060624163845.L1114>