From owner-freebsd-current Fri Sep 17 9:34:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id F304E14E07 for ; Fri, 17 Sep 1999 09:34:32 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA46928; Fri, 17 Sep 1999 09:34:22 -0700 (PDT) Date: Fri, 17 Sep 1999 09:34:29 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Matthew Dillon Cc: Dan Nelson , Brad Knowles , Thomas Dean , freebsd-current@FreeBSD.ORG Subject: Re: More benchmarking stuff... In-Reply-To: <199909171611.JAA53554@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Sep 1999, Matthew Dillon wrote: > :> files sitting in unflushed disk caches and you reboot, those files are > :> lost. Softupdated just guarantees that the disk will be in a stable > :> state after a crash, not that all data written before the crash will be > :> available. > :> > : > :Soft updates guarantees that when an fsync() is done, it's on disk... > > Actually.... it doesn't. I wish it did. All softupdates does is > guarentee that the on-disk image is stable, it doesn't guarentee > that the on-disk image has been synchronized to what the program > thinks it has written to the file. According to kirk FSYNC() does the right thing and 'sync()' doesn't. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message