From owner-freebsd-current Fri Sep 17 8:56:20 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 4374815513 for ; Fri, 17 Sep 1999 08:56:14 -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 IAA45556; Fri, 17 Sep 1999 08:55:52 -0700 (PDT) Date: Fri, 17 Sep 1999 08:55:59 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Dan Nelson Cc: Brad Knowles , Thomas Dean , freebsd-current@FreeBSD.ORG Subject: Re: More benchmarking stuff... In-Reply-To: <19990917104608.A55059@dan.emsphone.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, Dan Nelson wrote: > In the last episode (Sep 17), Brad Knowles said: > > At 8:05 AM -0700 1999/9/17, Thomas Dean wrote: > > > Are the files deleted before they are actually written to disk? > > > > Good question. I don't know the answer. I know that the > > process is to create all the files first, then operate on them > > (including deletions and more creations), and then finally do a > > removal of all of them as quickly as possible at the end of the test. > > > > I'd be willing to guess a lot of files do get created and then > > deleted before the data ever gets written to disk. After all, > > postmark was written to simulate the kind of a load that a > > heavily-used mail system places on the machine, and that's precisely > > the sort of environment where something like softupdates or mounting > > filesystems async does tend to help the most. > > Hmm. But when you're running a mail spool, you _want_ your files to > get committed to disk, don't you? If you've got (guessing) 500 spool > 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... > Don't NetApps do logging, so if the system crashes, the files are > recovered from the log? > > -- > Dan Nelson > dnelson@emsphone.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message