From owner-freebsd-current@FreeBSD.ORG Mon Jun 19 18:58:01 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FD7F16A5B0; Mon, 19 Jun 2006 18:58:01 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF73243D46; Mon, 19 Jun 2006 18:58:00 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k5JIw0pg023502; Mon, 19 Jun 2006 11:58:00 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k5JIw0Hd023501; Mon, 19 Jun 2006 11:58:00 -0700 Date: Mon, 19 Jun 2006 11:58:00 -0700 From: Brooks Davis To: Pawel Jakub Dawidek Message-ID: <20060619185800.GA22546@odin.ac.hmc.edu> References: <20060619131101.GD1130@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <20060619131101.GD1130@garage.freebsd.pl> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, freebsd-geom@freebsd.org Subject: Re: Journaling UFS with gjournal. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2006 18:58:01 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 19, 2006 at 03:11:01PM +0200, Pawel Jakub Dawidek wrote: >=20 > How it works (in short). You may define one or two providers which > gjournal will use. If one provider is given, it will be used for both - > data and journal. If two providers are given, one will be used for data > and one for journal. > Every few seconds (you may define how many) journal is terminated and > marked as consistent and gjournal starts to copy data from it to the > data provider. In the same time new data are stored in new journal. > Let's call the moment in which journal is terminated as "journal switch". Cool solution! I think I'll give this a try on my redundent mirror server at work. I'd be curious to see how gjournal performs with the journal on a battery backed ram disk like the gigabyte i-RAM: http://www.giga-byte.com/Products/Storage/Products_Overview.aspx?ProductID= =3D2180&ProductName=3DGC-RAMDISK It seems like that could reduce or eliminate many of the performance issues in practice. -- Brooks --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFElvO3XY6L6fI4GtQRAleqAKDQVc6j/LfjPPt4vcvqzz7osVfQbACdFErw Jo9Xaa7JuVQmsQw2u4ohwSQ= =q1/p -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--