From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 19:17:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8757B16A41F for ; Sat, 30 Jul 2005 19:17:22 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BA4C43D45 for ; Sat, 30 Jul 2005 19:17:22 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 030D62090EB; Sat, 30 Jul 2005 12:17:22 -0700 (PDT) Received: from [192.168.2.3] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j6UJHKX1078994; Sat, 30 Jul 2005 12:17:21 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <42EBD240.9090208@elischer.org> Date: Sat, 30 Jul 2005 12:17:20 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050424 X-Accept-Language: en, hu MIME-Version: 1.0 To: Poul-Henning Kamp References: <98853.1122719635@phk.freebsd.dk> In-Reply-To: <98853.1122719635@phk.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Apparent strange disk behaviour in 6.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2005 19:17:22 -0000 Poul-Henning Kamp wrote: > In message <42EB5687.2070400@elischer.org>, Julian Elischer writes: > >>Poul-Henning Kamp wrote: >> >>>In message <42E88135.30603@elischer.org>, Julian Elischer writes: >>> >>>Please use gstat and look at the service times instead of the >>>busy percentage. >> >>The snapshot below is typical when doing tar from one drive to another.. >>(tar c -C /disk1 f- .|tar x -C /disk2 -f - ) >> >>dT: 1.052 flag_I 1000000us sizeof 240 i -1 >> L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name >> 0 405 405 1057 0.2 0 0 0.0 0 0 0.0 9.8 | ad0 >> 0 405 405 1057 0.3 0 0 0.0 0 0 0.0 11.0 | ad0s2 >> 0 866 3 46 0.4 863 8459 0.7 0 0 0.0 63.8 | da0 >> 25 866 3 46 0.5 863 8459 0.8 0 0 0.0 66.1 | da0s1 >> 0 405 405 1057 0.3 0 0 0.0 0 0 0.0 12.1 | ad0s2f >> 195 866 3 46 0.5 863 8459 0.8 0 0 0.0 68.1 | da0s1d >> >>even though the process should be disk limitted neither of the disks is anywhere >>near 100%. > > > This looks like an awful lot of small files since you write 8 times as much data > as you read ? > > Since the write service time (ms/w) is low, I pressume you have > some hefty disk hardware (with cache ?) > > Presumably you're using softupdates ? > > I wouldn't be surprised if you were limited by system time rather than disk in > this scenario ? system is 87% idle >