vmstat 'b' (disk busy?) field keeps climbing ...

Marc G. Fournier scrappy at hub.org
Mon Jun 26 20:14:04 UTC 2006

I think I might have found *at least* one of the problems, and that being 
the excessively high blocked states while ps isn't finding anything ...


We just recently started allowing clients to run a MySQL server *within* 
their vServer ... in a drastic move, I just shut them all down on pluto, 
and blocked drop'd from ~86 down to 5 in a matter of moments ... 
restarting them all has it climbing once more, being up around 22 already 

I'm going to go with that theory for now, and keep an eye on things ...

Just curious as to why, even with -H, its not showing any blocked states 
within ps though ... ?


On Mon, 26 Jun 2006, Kostik Belousov wrote:

> On Mon, Jun 26, 2006 at 02:20:12AM -0300, Marc G. Fournier wrote:
>> On Mon, 26 Jun 2006, Kostik Belousov wrote:
>>> Yes, this looks like a deadlock. As I understand, that's on 6.1-STABLE ?
>> Yes, kernel sources, it seems, from May 25th, according to my /usr/src
>> tree ...
>>> BTW, do you use snapshots ?
>> Not that I've explicitly enabled ...
>>> I think that without ddb access, diagnose and debug the problem would be
>>> quite hard.
>> Would it be a simple matter of:
>> panic
>> to get it to dump core?  Or would more be involved?  Would a core dump
>> even work?
> Core dumps are somewhat unconvenient in this situation. Better,
> sending report to me, follow my advise in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html

Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy at hub.org                              MSN . scrappy at hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664

More information about the freebsd-stable mailing list