From owner-freebsd-questions Mon Aug 30 19: 5:26 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7A9C8151DF for ; Mon, 30 Aug 1999 19:05:23 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.8.8/8.8.8) with ESMTP id MAA22607; Mon, 30 Aug 1999 12:19:57 -0700 (PDT) (envelope-from bright@wintelcom.net) Date: Mon, 30 Aug 1999 19:19:57 +0000 (GMT) From: Alfred Perlstein To: Gary Schrock Cc: freebsd-questions@FreeBSD.ORG Subject: Re: tools for checking disk load? In-Reply-To: <4.2.0.58.19990830211508.00a2c4d0@eyelab.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Aug 1999, Gary Schrock wrote: > Ok, I thought I had sent this question before, but I don't think I ever saw > it go through, so I figure it disappeared into the ether somewhere, so I'll > give it another shot (been a week or two since I first sent it, I'm not > getting impatient at normal propagation times). > > Are there any usefull tools floating around that would help determine > whether a disk is being overloaded? I've got some suspicions that one of > the disks is running into periods of load causing problems for hte rest of > the system, but I'd like to get some hard numbers before we start > considering some upgrades. I know when I read the archives I saw some > discussion about expanding iostat to give more statistics that would be > useful for this (since msps seems to be useless), but this was all in 1995, > and nothing seems to have come of it. try "iostat" and "systat -iostat" good luck, -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message