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
> [EMAIL PROTECTED]
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
