From owner-freebsd-current Mon May 4 21:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16996 for freebsd-current-outgoing; Mon, 4 May 1998 21:17:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16990 for ; Mon, 4 May 1998 21:17:06 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id VAA28614 for ; Mon, 4 May 1998 21:14:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028610; Tue May 5 04:14:12 1998 Message-ID: <354E9212.500F9F30@whistle.com> Date: Mon, 04 May 1998 21:14:10 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Soft update code looking very stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a lot of heavy testing in the last five days, And the discovery of a mis-commit in the -current tree, It appears that the soft-update code is stable enough for wider testing. This is not to say that it is ABSOLUTLY correct, but it is faster than the current FS in SYNC mode and SAFER than it as well. The resolution of the current hickups will just make it MUCH safer. to test it you need a very current (read TODAY) snapshot of -current and the files from: http://www.freebsd.org/~julian I have also been runing it today in testing together with the DEVFS/SLICE options, and the we seem to have removed the incompatibility between those two options as well. :-) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message