Re: Spinning down drives

Willem Riede (wriede@monmouth.com)
Fri, 04 Jul 1997 12:54:14 -0400

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Pawel S. Veselov: "ext2_free_block already cleared for block xxxx"
Previous message: Nigel Metheringham: "System performance with more RAM than can be cached"
Maybe in reply to: Richard Gooch: "Spinning down drives"

On Sat, 5 Jul 1997, Richard Gooch <rgooch@atnf.CSIRO.AU> wrote:
> I tried mounting filesystems with -o noatime and that didn't help. I
> then ran update (bdflush) with -f 300 to set the timeout to 5
> minutes. That worked. It still seems odd that bdflush (1, NULL) will
> write to the disc if *no process has written to the disc since the
> last call to bdflush*. Doesn't the kernel properly tag all buffers as
> clean once bdflush is done?
>
If I'm not mistaken, it is standard Unix behaviour to write the time to the superblock of the disk - could that be it?

Regards, Willem Riede.

Next message: Pawel S. Veselov: "ext2_free_block already cleared for block xxxx"
Previous message: Nigel Metheringham: "System performance with more RAM than can be cached"
Maybe in reply to: Richard Gooch: "Spinning down drives"