From owner-freebsd-hardware@FreeBSD.ORG  Tue Oct 12 18:44:40 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
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 AD76016A4CE
	for <freebsd-hardware@freebsd.org>;
	Tue, 12 Oct 2004 18:44:40 +0000 (GMT)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 54ADD43D45
	for <freebsd-hardware@freebsd.org>;
	Tue, 12 Oct 2004 18:44:40 +0000 (GMT)
	(envelope-from Roisin.Murphy@gmail.com)
Received: by mproxy.gmail.com with SMTP id 79so419459rnk
	for <freebsd-hardware@freebsd.org>;
	Tue, 12 Oct 2004 11:44:39 -0700 (PDT)
Received: by 10.38.96.30 with SMTP id t30mr2433838rnb;
        Tue, 12 Oct 2004 11:44:39 -0700 (PDT)
Received: by 10.38.171.45 with HTTP; Tue, 12 Oct 2004 11:44:39 -0700 (PDT)
Message-ID: <b21e6cca0410121144420fe03b@mail.gmail.com>
Date: Tue, 12 Oct 2004 11:44:39 -0700
From: Roisin Murphy <Roisin.Murphy@gmail.com>
To: "Kenneth D. Merry" <ken@freebsd.org>
In-Reply-To: <20041012171106.GB86646@nargothrond.kdm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <b21e6cca041010181932879aeb@mail.gmail.com>
	 <20041011043508.GA72113@nargothrond.kdm.org>
	 <b21e6cca041011090816a1352@mail.gmail.com>
	 <20041011210303.GA78436@nargothrond.kdm.org>
	 <b21e6cca04101117425d2908eb@mail.gmail.com>
	 <20041012171106.GB86646@nargothrond.kdm.org>
cc: freebsd-hardware@freebsd.org
Subject: Re: sata raid & write cache state
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Roisin Murphy <Roisin.Murphy@gmail.com>
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2004 18:44:40 -0000

> The main point of write back caching is to give the user faster turnaround
> for their commands without the application having to support deep queueing.

1. that is now taken care of by the 'write back' cache on the raid
controller. So (s)ata raid setups can still perform similarly to scsi
setups. But enough about that :)
anyway, enough of that :)


> Sure, you can recover from a power outage, you just have to scrub the array
> when you come back up.  You also won't know for sure whether you have some
> data corruption.

2. how do you usually 'scrub' the array? is this automatically done by
the controller when it boots up? or does this usually require the user
issuing commands via those raid CLIs?

3. one more thing about the battery back up option, now that i thought
about it, it has to be like a mini PSU that has enough power to keep
all the disks spinning for couple seconds after your main psu/power
dies, so now i understand why it cost $100+