From owner-freebsd-hackers Fri Jun 30 0:17:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from skaarup.org (skaarup.org [130.228.230.140]) by hub.freebsd.org (Postfix) with ESMTP id 8D5EC37B62B for ; Fri, 30 Jun 2000 00:17:30 -0700 (PDT) (envelope-from rasmus@gal.dk) Received: from localhost (skaarup@localhost) by skaarup.org (8.9.3/8.9.3) with ESMTP id JAA54518; Fri, 30 Jun 2000 09:16:33 +0200 (CEST) (envelope-from rasmus@gal.dk) Date: Fri, 30 Jun 2000 09:16:33 +0200 (CEST) From: Rasmus Skaarup X-Sender: skaarup@skaarup.org To: Soren Schmidt Cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: vinum and superblocks. In-Reply-To: <200006300704.JAA85601@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Jun 2000, Soren Schmidt wrote: > It seems Jaye Mathisen wrote: > > > > I have 8 75GB IBM drives striped in a big raid 0 for monkeying with. > > > > newfs -i 131072 -v /dev/vinum/bighonkindisk seems to very nicely put all > > the data that newfs write out on to the first disk... It least, only the > > first disk gets any io, accoring to systat and iostat. > > You need to adjust your stripe size so that the superblocks etc are > not all put on the same disk, ie some odd stripe size is often best > to distribute those to hopefully all disks... By 'odd', you mean small, Søren? If this is the case, be careful not to make the size too small, which will degrade the perfomance because of the Jaye, are you sure you doing a large (preferrebly at least one GB) sequential read or write from/to your disks? If you are only doing small random I/O, this could result in only one disk getting hit. But it does sound strange that when making the filsystem, only the first disk gets initialized.. Are you positively sure about this? The size of the vinum volume corresponds to approx 8 * 75GB ? Best regards Rasmus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message