From owner-freebsd-hackers Fri Jun 30 0: 4:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8AFA137C36C for ; Fri, 30 Jun 2000 00:04:29 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA85601; Fri, 30 Jun 2000 09:04:25 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200006300704.JAA85601@freebsd.dk> Subject: Re: vinum and superblocks. In-Reply-To: from Jaye Mathisen at "Jun 29, 2000 03:00:59 pm" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Fri, 30 Jun 2000 09:04:25 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Jaye Mathisen wrote: > Not sure what the right thing to do here is, or even if it's a real > problem, but: > > 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. > > Which would seem to me to be problematic in terms of using fsck -b, and > also just for the fact that it would seem that you would have to hit that > disk more often than the others, even though it's striped. > > I realize there's no protection with the raid 0, but the load doesn't seem > evenly distributed on a transaction basis, even though the data is evenly > spread. > > What's the right thing to do here? 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... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message