From owner-freebsd-stable@FreeBSD.ORG Tue Oct 31 22:17:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44F9916A4AB for ; Tue, 31 Oct 2006 22:17:31 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01EBF43D5A for ; Tue, 31 Oct 2006 22:16:30 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Gf1u0-00011F-Ff for freebsd-stable@freebsd.org; Tue, 31 Oct 2006 23:16:12 +0100 Received: from 89-172-44-80.adsl.net.t-com.hr ([89.172.44.80]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 Oct 2006 23:16:12 +0100 Received: from ivoras by 89-172-44-80.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 Oct 2006 23:16:12 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 31 Oct 2006 23:16:12 +0100 Lines: 9 Message-ID: References: <45470D95.5020801@qbrick.com> <454718DD.8060108@qbrick.com> <45471ACC.2030604@fer.hr> <4547421D.2010206@qbrick.com> <45477FCC.9050901@qbrick.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-44-80.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: <45477FCC.9050901@qbrick.com> Sender: news Subject: Re: SAS Raid - mfi driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 22:17:31 -0000 Fredrik Widlund wrote: > Solved my issue with LSI 8480E without BBU. With "write: BadBBU", > "cache: enabled", and "io: cached", performance rose to around 200MB/s > from 20MB/s. I don't know what "BadBBU" is, but from some Googling it seems to be a setting that overrides BBU detection, and enables write caching even if the system believes BBU is broken or missing. If true, this may be dangerous for data consistency.