From owner-freebsd-current@FreeBSD.ORG Mon Dec 19 15:28:18 2005 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 B642216A41F for ; Mon, 19 Dec 2005 15:28:18 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm2.irt.drexel.edu [144.118.29.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1DA143D49 for ; Mon, 19 Dec 2005 15:28:17 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id DA02411667D for ; Mon, 19 Dec 2005 10:28:16 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id D3E5F1165D5 for ; Mon, 19 Dec 2005 10:28:16 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [129.25.6.250]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jBJFS8P0067226 for ; Mon, 19 Dec 2005 10:28:08 -0500 (EST) (envelope-from jsmith@drexel.edu) Message-ID: <43A6D190.3020504@drexel.edu> Date: Mon, 19 Dec 2005 10:28:16 -0500 From: Justin Smith User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: "Native" journaling file systems? 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 Dec 2005 15:28:18 -0000 Are there any plans to develop UFS3--- i.e., a UFS2 file system with an added journal? I've used several journaling file systems in Linux and like the Reiser FS except for one MAJOR drawback: When something goes wrong, reiser-fsck absolutely sucks at repairing things (Hans Reiser freely admits that but says it's never needed because nothing ever goes wrong). Businesses that use the reiser file system have to buy expensive commercial products for fixing it (there are at least two on the market). Ext3 works well and one always has the standard fsck to fall back on if something goes wrong. One can also easily convert an existing Ext2 file system to Ext3. After a crash, replaying the journal only takes a second or two. A UFS3 might have the same desirable features.