From owner-freebsd-questions@FreeBSD.ORG Sun Aug 17 09:37:42 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B7F37B404 for ; Sun, 17 Aug 2003 09:37:42 -0700 (PDT) Received: from nitrogen.nocdirect.com (nitrogen.nocdirect.com [66.227.56.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85A6443F93 for ; Sun, 17 Aug 2003 09:37:41 -0700 (PDT) (envelope-from dpuryear@usa.net) Received: from d-185-56-nospr3.i-55.com ([209.205.185.56] helo=dpboxen.usa.net) by nitrogen.nocdirect.com with esmtp (Exim 4.20) id 19oQX4-0001lh-Gr; Sun, 17 Aug 2003 11:37:30 -0500 Message-Id: <5.2.1.1.0.20030817111037.02be2e60@pop.netaddress.com> X-Sender: dpuryear@pop.netaddress.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Sun, 17 Aug 2003 11:14:10 -0500 To: Rus Foster , questions@freebsd.org From: Dustin Puryear In-Reply-To: <20030810142709.K1213@thor.65535.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - nitrogen.nocdirect.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - usa.net Subject: Re: Which process are waiting for I/O? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 16:37:42 -0000 At 02:28 PM 8/10/2003 -0700, Rus Foster wrote: >Hi All, >I've got a box which is getting high loads as process are starting waiting >for I/O but I can't track down the process as I think they stop/start >quickly. Any ideas of how to track it down? Yes. You need to enable process accounting using accton: # accton /var/account/acct Let the processes that you suspect are causing issues run for a bit. Next, use sa to determine what the heck is going on. You can get a lot of detail out of sa so make sure to read the manpage. You may also want to run bsdsar (in ports) to watch for higher-level issues while using sa to get the real detail. /var/account/acct is going to grow pretty fast. Be sure to rotate it if you plan on leaving process accounting enabled after your troubleshooting. --- Dustin Puryear Puryear Information Technology, LLC Providing expertise in the management, integration, and security of Windows and UNIX systems, networks, and applications.