From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 5 12:10:19 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 184D016A557 for ; Thu, 5 Feb 2004 12:10:19 -0800 (PST) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F03343D66 for ; Thu, 5 Feb 2004 12:10:03 -0800 (PST) (envelope-from listac@nebelschwaden.de) Received: from port-212-202-176-125.reverse.qdsl-home.de ([212.202.176.125] helo=kaperfahrt.nebelschwaden.de) by mx02.qsc.de with esmtp (Exim 3.35 #1) id 1Aopnq-0000VD-00 for freebsd-hardware@freebsd.org; Thu, 05 Feb 2004 21:08:46 +0100 Received: from sturmwarnung.nebelschwaden.de (sturmwarnung.nebelschwaden.de [172.16.37.19]) by kaperfahrt.nebelschwaden.de (Postfix) with ESMTP id 2C4984A5 for ; Thu, 5 Feb 2004 21:08:44 +0100 (CET) Received: from nebelschwaden.de (localhost.nebelschwaden.de [127.0.0.1]) by sturmwarnung.nebelschwaden.de (Postfix) with ESMTP id 74A2F265 for ; Thu, 5 Feb 2004 21:08:47 +0100 (CET) Message-ID: <4022A2CE.5040504@nebelschwaden.de> Date: Thu, 05 Feb 2004 21:08:46 +0100 From: Ede Wolf User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040103 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <002401c3e661$32b27c00$0c00a8c0@artem> <401FE932.9060401@web.de> In-Reply-To: <401FE932.9060401@web.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: SATA RAID 5 controller for FreeBSD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: listac@nebelschwaden.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 20:10:19 -0000 > It does not have cache as the hard disks and the OS have. There is no need. I am by no means a RAID expert and this might be slightly off topic, but I've realized, that SCSI-Disks used in a RAID always have their write-cache disabled. Not sure why, but I guess partly for control meaning that if the controller flushes its cache, it can be sure that data is on the disk. With write cache enabled, the controler has no real knowledge of the state of the drives and may be "confused" by extremely different speeds (writing data to an empty cache on drive 1 while drive 2 is busy writing its own cache to disk). So basically the cache on the controller is an replacement for those on the drives. This may be complete bollocks, only what I've been told, but maybe someone would be so kind to clearify, since I am not aware one can disable write cache on ATA drives. Which even may not be relevant.