From owner-freebsd-stable Tue Jul 11 21: 6:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id E6FAB37BB6F for ; Tue, 11 Jul 2000 21:06:42 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 13CDnB-000B8o-00; Tue, 11 Jul 2000 21:06:37 -0700 Date: Tue, 11 Jul 2000 21:06:31 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Richard Stanaford Cc: Paul Coyne , freebsd-stable@freebsd.org Subject: Re: Cached versus non cached disk I/O In-Reply-To: <20000712025107.15159.qmail@web3106.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jul 2000, Richard Stanaford wrote: > --- Tom wrote: > > On Tue, 11 Jul 2000, Paul Coyne wrote: > > > The filesystem can be put into async (or softupdates) mode so that > > local metadata update functions return before the metadata is actualy > > written to disk. > > Doesn't 'asyncing' the filesystem make it more fragile? Or did I read the > Handbook/Making the World section wrong? Yes it does, but I made no statement saying it was fragile or not. It should be obvious that write-buffering metadata can cause problems, even with softupdates, though softupdates is clearly better than async. > -Richard Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message