From owner-freebsd-fs Wed Feb 12 19:41:44 2003 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD77637B401; Wed, 12 Feb 2003 19:41:43 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF3843FA3; Wed, 12 Feb 2003 19:41:43 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0418.cvx22-bradley.dialup.earthlink.net ([209.179.199.163] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18jAFY-00031C-00; Wed, 12 Feb 2003 19:41:25 -0800 Message-ID: <3E4B138F.26E32E75@mindspring.com> Date: Wed, 12 Feb 2003 19:40:00 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Darren Pilgrim Cc: Matthew Emmerton , David Schultz , Daxbert , Bill Moran , Heinrich Rebehn , freebsd-questions@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Why is there no JFS? References: <3E4A5B77.5080103@ant.uni-bremen.de> <3E4A863E.2030801@potentialtech.com> <3E4A8EF5.1070308@ant.uni-bremen.de> <3E4A9712.8030609@potentialtech.com> <3E4AA331.5040701@ant.uni-bremen.de> <3E4AA734.5040102@potentialtech.com> <045401c2d2db$f9d45c30$0a0aa8c0@dweebsoft.com> <20030212225631.GA10375@HAL9000.homeunix.com> <005801c2d2eb$aa5fae60$1200a8c0@gsicomp.on.ca> <3E4ADDDE.5040208@pantherdragon.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4dfa0e541153ecfc11414c96ce2d021343ca473d225a0f487350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Darren Pilgrim wrote: > Not really. A properly laid-out filesystem hierarchy will result in no > writes to / (except for installworld/kernel). That removes the problem > that journalling addresses, and is probably why softupdates is disabled > by default for /. For large, active filesystems, journalling would be a > big improvement when you had to run a foreground fsck. Soft updates are disable on / by default because of the chicken and egg problem of runing tunefs on /. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message