From owner-freebsd-questions Mon Aug 23 17:59:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id 2A55214E66 for ; Mon, 23 Aug 1999 17:59:12 -0700 (PDT) (envelope-from gary@eyelab.psy.msu.edu) Received: from piper (dyn1-tnt10-182.detroit.mi.ameritech.net [209.18.29.182]) by eyelab.psy.msu.edu (8.9.3/8.9.2) with ESMTP id UAA43686 for ; Mon, 23 Aug 1999 20:59:09 -0400 (EDT) (envelope-from gary@eyelab.psy.msu.edu) Message-Id: <4.2.0.58.19990823204323.00a2c830@eyelab.msu.edu> X-Sender: gary@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 23 Aug 1999 20:47:20 -0400 To: freebsd-questions@freebsd.org From: Gary Schrock Subject: tools for checking disk load? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. The system is currently running 2.2-stable (we're planning on upgrading, but it's not in a convenient location to have someone there to do the upgrade and since it's been working fine we've been putting it off). Thanks, Gary Schrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message