From owner-freebsd-geom@FreeBSD.ORG Sat May 5 15:31:05 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 316B016A400 for ; Sat, 5 May 2007 15:31:05 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id E8CE613C45E for ; Sat, 5 May 2007 15:31:04 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 4567D20A7; Sat, 5 May 2007 17:31:01 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 38D00208C; Sat, 5 May 2007 17:31:01 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 1988B48A6; Sat, 5 May 2007 17:31:01 +0200 (CEST) From: des@des.no (Dag-Erling =?utf-8?Q?Sm=C3=B8rgrav?=) To: Ivan Voras References: <171980743.20070504223126@uzvik.kiev.ua> <125507.38194.qm@web30304.mail.mud.yahoo.com> Date: Sat, 05 May 2007 17:31:00 +0200 In-Reply-To: (Ivan Voras's message of "Sat, 05 May 2007 16:20:51 +0200") Message-ID: <86fy6bqocr.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-geom@freebsd.org Subject: Re: graid5 after-reboot problem X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2007 15:31:05 -0000 Ivan Voras writes: > Is the write cache in graid5 aware of what happens on the VFS / UFS > layers (something like gjournal does)? Otherwise, how can you guarantee > consistency with write caching at the GEOM layer when there's a power > outage or some other system interruption? You can't. Google for "RAID 5 write hole" for an explanation. The way this is handled by hardware RAID 5 controllers is that they keep a journal in the controller's memory (which has its own battery backup) and replay it when the power returns. If the controller is fried, you're SOL. ZFS uses copy-on-write, so its raidz and raidz2 do not have a "write hole". DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no