From owner-freebsd-questions Wed Feb 4 16:48:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22956 for questions-outgoing; Wed, 4 Feb 1998 16:48:48 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22946 for ; Wed, 4 Feb 1998 16:48:36 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id QAA16494; Wed, 4 Feb 1998 16:48:29 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 4 Feb 1998 16:48:29 -0800 (PST) From: Doug White Reply-To: Doug White To: roark_hilomen_at_meridian@meridian-data.com cc: freebsd-questions@FreeBSD.ORG Subject: Re: Soft Updates In-Reply-To: <9802048866.AA886625156@meridian-data.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" On Wed, 4 Feb 1998 roark_hilomen_at_meridian@meridian-data.com wrote: > I was searching for "Soft Updates" implementation and found references to it in > the Filesystem newsgroup. Unfortunately it only mentioned that OpenBSD was > implementing it. It slightly hinted that FreeBSD may have it soon, but no > timeframe or release number (2.2.5? 3.0? 3.0+?) This hit the -hackers mailing list the other day and they are working out the licensing issues. If it does come into the tree it'll go into -CURRENT for shakeout. It won't ever come into 2.2.x most likely. > I am definitely interested in the "Soft Update" enhancemnet to the filesystem. > I would like to know its availability or current state of development. The I/O improvements quoted were _very_ impressive. > Also, since soft updates tend to delay "writes", on a critical failure (system > crash, panic, power outage), what provisions of data integrity have been > implemented? Is an intent log written out? Has fsck changed? It's probably as dangerous as running with asynchronous updates. If the system blows up with uncommitted writes then data could be lost. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major