From: Bart Samwel <bart@samwel.tk>
To: Micha Feigin <michf@post.tau.ac.il>
Cc: 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: Thu, 29 Jan 2004 13:51:01 +0100 [thread overview]
Message-ID: <401901B5.5080306@samwel.tk> (raw)
In-Reply-To: <20040128230609.GE3975@luna.mooo.com>
Micha Feigin wrote:
>>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.
>
> It might help you find the culprit. There is a laptopmode patch
> for 2.6. If you echo a number n larger then 1 into
> /proc/sys/vm/laptopmode it will dump the first n disk accesses to the
> console (The docs that come with the patch have the complete
> description).
This was true in the first version (for /proc/sys/vm/block_dump, not
laptop_mode), however, this approach was then shot down in favor of a
simple on/off flag.
--Bart
prev parent reply other threads:[~2004-01-29 12:51 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
2004-01-28 23:06 ` Micha Feigin
2004-01-29 12:51 ` Bart Samwel [this message]
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=401901B5.5080306@samwel.tk \
--to=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
--cc=michf@post.tau.ac.il \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox