All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lutz Vieweg <lkv@isg.de>
To: Bart Samwel <bart@samwel.tk>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Is there a way to keep the 2.6 kjournald from writing to idle disks? (to allow spin-downs)
Date: Wed, 28 Jan 2004 14:30:52 +0100	[thread overview]
Message-ID: <4017B98C.2040603@isg.de> (raw)
In-Reply-To: <4016B3F0.1060804@samwel.tk>

Bart Samwel wrote:

>> Well, it's the o.p. system, not mine, but I don't see how noatime will
>> help him, the atime shouldn't change unless he's doing disk access, and
>> if he's doing disk access the disk will spin up anyway.

That's what I thought, too... and I really killed everything that I could
imagine accessing the disk... but...

> If something really is accessing the drive, noatime might still help as 
> long as the accesses are from the cache.

... that really helped! I'm kind of surprised, since I didn't use noatime
before the update, and I still don't know of any process that might do
the reading, but since mounting / with noatime helped, I'm happy for now.

My curiosity isn't completely gone, though, so maybe one day I'll try to
find out who-is-trying-to-read-what, "find -atime ..." didn't reveal the secret
yet.

Regards,

Lutz Vieweg



  reply	other threads:[~2004-01-28 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 18:29 Is there a way to keep the 2.6 kjournald from writing to idle disks? (to allow spin-downs) Lutz Vieweg
2004-01-25 18:33 ` Andreas Dilger
2004-01-25 18:56 ` Matthias Andree
2004-01-25 19:26 ` Felipe Alfaro Solana
2004-01-26 10:16   ` Lutz Vieweg
2004-01-26 10:43     ` Nick Piggin
2004-01-26 10:43     ` Bart Samwel
2004-01-25 20:52 ` Micha Feigin
2004-01-27  0:21   ` bill davidsen
2004-01-27 15:16     ` Bart Samwel
2004-01-27 18:44       ` Bill Davidsen
2004-01-27 18:54         ` Bart Samwel
2004-01-28 13:30           ` Lutz Vieweg [this message]
2004-01-28 23:06             ` Micha Feigin
2004-01-29 12:51               ` Bart Samwel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4017B98C.2040603@isg.de \
    --to=lkv@isg.de \
    --cc=bart@samwel.tk \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.