From owner-freebsd-hardware@FreeBSD.ORG Fri Sep 19 06:23:50 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0335F1065674 for ; Fri, 19 Sep 2008 06:23:50 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id DA2CE8FC15 for ; Fri, 19 Sep 2008 06:23:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by QMTA02.emeryville.ca.mail.comcast.net with comcast id GVnP1a0021HpZEsA2WPpdd; Fri, 19 Sep 2008 06:23:49 +0000 Received: from koitsu.dyndns.org ([67.180.253.227]) by OMTA14.emeryville.ca.mail.comcast.net with comcast id GWPo1a0014v8bD78aWPoT3; Fri, 19 Sep 2008 06:23:49 +0000 X-Authority-Analysis: v=1.0 c=1 a=Cwt2jS5HOtoA:10 a=zpwKT23VM_0A:10 a=QycZ5dHgAAAA:8 a=2yFjQ_jmp9e9Tl4sVNAA:9 a=LrZClurUzweosR3dAxECjUO-AWUA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 4FB3117B81A; Thu, 18 Sep 2008 23:23:48 -0700 (PDT) Date: Thu, 18 Sep 2008 23:23:48 -0700 From: Jeremy Chadwick To: Dieter Message-ID: <20080919062348.GA37673@icarus.home.lan> References: <48D31C82.8030007@fluffles.net> <200809190548.FAA08998@sopwith.solgatos.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200809190548.FAA08998@sopwith.solgatos.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hardware@freebsd.org Subject: Re: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2008 06:23:50 -0000 On Thu, Sep 18, 2008 at 10:48:03PM +0100, Dieter wrote: > > If you get about the same scores with dd, try using a higher read-ahead > > (vfs.read_max value, set it to 32 for example). Also sometimes it's > > required to use a higher blocksize to get full potential, try: > > > > newfs -U -b 32768 /dev/ > > > > Warning: using 64KiB blocksize you risk hanging the system under heavy > > load (like 2 bonnies running simultaniously). > > What's this about 64KiB blocksize hanging the system? > Hang awhile then recover, or hang forever need a reboot? > Is this a RAID thing or are normal disks at risk? > It isn't obvious why a 64KiB blocksize would cause a > problem in this day of multi GiB memory. Why do you think the amount of memory people have in their computers has *anything* to do with a filesystem blocksize? If a large blocksize would crash a filesystem, it's not going to be due to "not having enough RAM". -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |