From owner-freebsd-current Fri Sep 17 16:59:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from pike.sover.net (pike.sover.net [209.198.87.34]) by hub.freebsd.org (Postfix) with ESMTP id 4BC131519C for ; Fri, 17 Sep 1999 16:59:38 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a335.bf.sover.net [209.198.83.243]) by pike.sover.net (8.9.3/8.9.3) with ESMTP id TAA00441; Fri, 17 Sep 1999 19:59:31 -0400 (EDT) Comments: SoVerNet Verification (on pike.sover.net) nightfall.digitalspark.net from arc0a335.bf.sover.net [209.198.83.243] 209.198.83.243 Fri, 17 Sep 1999 19:59:31 -0400 (EDT) Date: Fri, 17 Sep 1999 20:03:19 +0000 (GMT) From: Adam Strohl 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 Actually, the IIRC, NetApps have NVRAM cache, powering the thing down and back up doesn't change anything. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - 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. > > 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