From: Elias Oltmanns <eo@nebensachen.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Keeping track of spin-down/spin-up and causes of spin-up?
Date: Tue, 08 Jul 2008 10:07:12 +0200 [thread overview]
Message-ID: <87hcb0kde7.fsf@denkblock.local> (raw)
In-Reply-To: <jwvskuku9jr.fsf-monnier+gmane.linux.kernel@gnu.org> (Stefan Monnier's message of "Tue, 08 Jul 2008 03:25:18 -0400")
With reference to the subject, are you a physicist by any chance? ;-)
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
[...]
> In any case, I have a machine here whose disk keeps spinning back up
> on a regular basis, and I can't seem to find any correlated event.
> Is there a tool that can help me track down the reason why the disk
> is accessed?
You can do
# echo 1 > /proc/sys/vm/block_dump
temporarily, so all disk accesses will be logged in dmesg. You should
seriously consider stopping klogd first because your log files will be
swamped otherwise.
That reminds me that syslog could well be the reason for your disk to
spin up frequently. But then you might have thought of that already.
Regards,
Elias
prev parent reply other threads:[~2008-07-08 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 7:25 Keeping track of spin-down/spin-up and causes of spin-up? Stefan Monnier
2008-07-08 7:48 ` Tino Keitel
2008-07-08 8:07 ` Elias Oltmanns [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=87hcb0kde7.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=monnier@iro.umontreal.ca \
/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