Date: Thu, 18 Sep 2008 23:23:48 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Dieter <freebsd@sopwith.solgatos.com> Cc: freebsd-hardware@freebsd.org Subject: Re: Test: HighPoint RocketRaid 3120 PCIex1 2xSATA controller under FreeBSD 7.1-PRERELEASE Message-ID: <20080919062348.GA37673@icarus.home.lan> In-Reply-To: <200809190548.FAA08998@sopwith.solgatos.com> References: <48D31C82.8030007@fluffles.net> <200809190548.FAA08998@sopwith.solgatos.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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/<raid device> > > > > 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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080919062348.GA37673>