From owner-freebsd-current Thu Jan 7 22:33:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10349 for freebsd-current-outgoing; Thu, 7 Jan 1999 22:33:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10342 for ; Thu, 7 Jan 1999 22:33:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA38081; Thu, 7 Jan 1999 22:32:55 -0800 (PST) (envelope-from dillon) Date: Thu, 7 Jan 1999 22:32:55 -0800 (PST) From: Matthew Dillon Message-Id: <199901080632.WAA38081@apollo.backplane.com> To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: SOFTUPDATES Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have seen all the messages about Softupdates, and such, and I was :wondering what the advantages of using Softupdates are (or will be once :the code is debugged). I have looked on the FreeBSD website, and couldn't :find this information there. : :Kenneth Culver Softupdates basically gives you the advantage of an async mount without any of the risks. It's actually better then that - it can unwind commits to disk before they occur ( e.g. if you create a temporary file and then delete it very soon after ). Softupdates basically guarentees disk consistancy in the face of a crash. It's pretty well debugged as it stands -- I'd call it production. I don't think the problem the person who was posting and calling a softupdates is actually a softupdates problem. I've been using it solidly for a while and BEST has been using it on their nntp box ( a very heavily loaded box ) for a few months. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message