From owner-freebsd-geom@FreeBSD.ORG Fri Sep 22 18:39:14 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25BD116A40F for ; Fri, 22 Sep 2006 18:39:14 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7404143D72 for ; Fri, 22 Sep 2006 18:39:12 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id DE3C648801; Fri, 22 Sep 2006 20:39:10 +0200 (CEST) Received: from localhost (dlw253.neoplus.adsl.tpnet.pl [83.24.52.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id ED69345B26; Fri, 22 Sep 2006 20:39:05 +0200 (CEST) Date: Fri, 22 Sep 2006 20:38:41 +0200 From: Pawel Jakub Dawidek To: "Rick C. Petty" Message-ID: <20060922183841.GA22578@garage.freebsd.pl> References: <20060921200909.GA13927@megan.kiwi-computer.com> <200609220914.k8M9E1h8077566@lurza.secnetix.de> <20060922133900.GA31626@megan.kiwi-computer.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20060922133900.GA31626@megan.kiwi-computer.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@FreeBSD.ORG Subject: Re: geom - help ... 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: Fri, 22 Sep 2006 18:39:14 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 22, 2006 at 08:39:00AM -0500, Rick C. Petty wrote: > I wouldn't say it's at all better, although it was easier to setup just a > mirror. Vinum is a volume manager, so I expect it to be more complex than > just setting up a mirror. But I certainly wouldn't call it better. My > mirror rebuilds *every* power outtage (and sometimes even at expected > shutdowns), a behavior I have not witnessed with gvinum. If gvinum doesn't rebuild mirrors after power failures when the device is open for writting, then it is a bug in gvinum. A reliable RAID system has to do it. Imagine a simple situation when write request is only stored on one component and a power failure prevents it to be stored on the rest of components. How can you be sure that the data is in a consistent state? There should be no rebuilds after clean shutdowns, if there are, please give me the details, because this is the first time I hear about it. For gmirror, even if device is open for write, one can define idle time after which device will be marked as clean. So after few seconds without writes, even on power failure no rebuild is needed. I've a code in perforce to avoid rebuilds even after a power failure, which can be used when gjournal is running on top of gmirror. For such configuration it is reliable. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFFC2xForvXbEpPzQRAvTvAKCpywUePrHoSapD0KsBQ/1CaCTwVgCgvtsm PQ8XAe82rUPYB7w9ovAdVm0= =B4aI -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB--