From: Kyle Liddell <kyle@foobox.homelinux.net>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Sat, 22 Aug 2009 01:02:44 -0400 [thread overview]
Message-ID: <1250917364.2889.29.camel@athlon> (raw)
In-Reply-To: <20090820163522.GA29215@sewage>
On Thu, 2009-08-20 at 11:35 -0500, Matt Garman wrote:
> So what I'm trying to figure out is, what is causing the disk
> access? It could be any one of:
>
> - Kernel
> - RAID subsystem (i.e. md)
> - XFS filesystem
> - NFS
> - Samba
> - ???
For one, syslogd.
It's probably worthwhile to look up information for laptop power saving.
In particular, laptop-mode in the kernel, and laptop-mode-tools:
http://samwel.tk/laptop_mode
I use this on my laptop, and I don't think I ever have a "surprise" disk
spinup. The whole laptop-mode-tools setup is probably much more than
you want, but it's a good place to start. The FAQ there also mentions
how to get syslog to stop syncing to disk.
You may also find 'lm-profiler' useful - this will tell you the which
process is causing disk accesses. Finally, for general power saving,
'powertop' tracks the power state information for your CPU, and will
list the processes that are causing your CPU to come out of any
sleep/idle states.
prev parent reply other threads:[~2009-08-22 5:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 16:35 linux disk access when idle Matt Garman
2009-08-20 18:45 ` Richard Scobie
2009-08-21 16:59 ` Matt Garman
2009-08-21 17:01 ` Ric Wheeler
2009-08-22 21:04 ` Matt Garman
2009-08-23 18:23 ` Bill Davidsen
2009-08-26 19:45 ` Matt Garman
2009-08-22 6:33 ` Goswin von Brederlow
2009-08-21 6:42 ` Henry, Andrew
2009-08-21 8:17 ` Jon Hardcastle
2009-08-21 16:35 ` Foster_Brian
2009-08-21 17:31 ` Matt Garman
2009-08-21 17:22 ` Matt Garman
2009-08-21 22:00 ` Bill Davidsen
2009-08-21 23:10 ` Matt Garman
2009-08-21 23:13 ` Carl A. Cook
2009-08-22 1:41 ` berk walker
2009-08-22 2:07 ` John Robinson
2009-08-22 4:28 ` Richard Scobie
2009-08-22 5:04 ` Tapani Tarvainen
2009-08-22 6:37 ` Goswin von Brederlow
2009-08-24 18:07 ` Billy Crook
2009-08-22 5:02 ` Kyle Liddell [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=1250917364.2889.29.camel@athlon \
--to=kyle@foobox.homelinux.net \
--cc=linux-raid@vger.kernel.org \
--cc=matthew.garman@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).