Date: Mon, 26 Jun 2006 08:22:46 -0400 From: Chuck Swiger <cswiger@mac.com> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: leaking blocked processes in vmstat ... how to debug? Message-ID: <449FD196.1020405@mac.com> In-Reply-To: <20060626082906.T1114@ganymede.hub.org> References: <20060626080344.X1114@ganymede.hub.org> <20060626082906.T1114@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc G. Fournier wrote: > Up to 48 right now, and still nothing to show for it ... Perhaps it is not clear to you that under Unix is it normal for processes to block waiting on events like user input, a signal indicating a timer has fired or a pipe has more data, etc. The reason you are looking for processes stuck in "D" for "Disk wait" state is to identify any large processes that are being swapped out and thus being held up by RAM limitations. On the other hand, it's entirely possible that you've simply got too much stuff running for the available hardware, and will need to either add RAM or offload some of the workload to other machines. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?449FD196.1020405>