From owner-freebsd-current Wed Oct 6 14:18:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 84F1D14C84 for ; Wed, 6 Oct 1999 14:18:51 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id QAA90799; Wed, 6 Oct 1999 16:18:16 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910062118.QAA90799@celery.dragondata.com> Subject: Re: make install trick To: fullermd@futuresouth.com (Matthew D. Fuller) Date: Wed, 6 Oct 1999 16:18:15 -0500 (CDT) Cc: peter.jeremy@alcatel.com.au (Peter Jeremy), bright@wintelcom.net (Alfred Perlstein), freebsd-current@FreeBSD.ORG In-Reply-To: <19991006154419.O20768@futuresouth.com> from "Matthew D. Fuller" at Oct 06, 1999 03:44:19 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Wed, Oct 06, 1999 at 02:57:23PM +1000, a little birdie told me > that Peter Jeremy remarked > > > > I guess we disagree on this. My feeling is that write activity on > > root should be minimised to minimise the risk that root will be > > inconsistent following a crash. > > Indeed. > Thus: > /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > ^^^^^^^^^^^ > > Though I'm still waiting for an explanation of WHY exactly I have async > writes on a sync partition. Nobody yet has said anything but 'that's > interesting...'. A direction to look would be helpful. > My understanding was that that was just a indication of writes that were able to be done asynchronously without any risk, so they were done async. (sync isn't purely sync, only synchronous when it's required for integrity) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message