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?
References: <jwvskuku9jr.fsf-monnier+gmane.linux.kernel@gnu.org>
Date: Tue, 08 Jul 2008 10:07:12 +0200
In-Reply-To: <jwvskuku9jr.fsf-monnier+gmane.linux.kernel@gnu.org> (Stefan
	Monnier's message of "Tue, 08 Jul 2008 03:25:18 -0400")
Message-ID: <87hcb0kde7.fsf@denkblock.local>
User-Agent: Gnus/5.110007 (No Gnus v0.7)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 962
Lines: 28

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/