linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Garman <matthew.garman@gmail.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Sat, 22 Aug 2009 16:04:44 -0500	[thread overview]
Message-ID: <20090822210443.GA12033@sewage> (raw)
In-Reply-To: <4A8ED2FC.2070700@redhat.com>

On Fri, Aug 21, 2009 at 01:01:48PM -0400, Ric Wheeler wrote:
> On 08/21/2009 12:59 PM, 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
>>>>      - ???
>>>>        
>>> Are you running smartd? It polls the drives every 30minutes.
>>    
> I think that you can use blktrace to see who is issuing the IO's
> that  spin up your drives....

For five hours today, I ran blktrace on md1 as well as the drives
that make up md1 (sd[a-d]).  I also enabled block dump via

    echo 1 > /proc/sys/vm/block_dump

Nothing.  Neither block_dump nor blktrace recorded anything on md1
or sd[abcd].  I caught one instance where the heads parked (I both
heard them park as well as saw the power meter show the 10 watt
drop).  They only stayed parked for about five minutes.  Yet neither
blktrace nor block_dump caught anything.

I'm going to try lm-profiler now (from the laptop-mode-tools
package), but I have low expectations.

I'm beginning to think that it's not even direct access to the
drives that cause the heads to unpark, e.g. perhaps even activity on
my system drive (a compact flash card connected to the PATA port)
prevents the data drives from parking their heads.


  reply	other threads:[~2009-08-22 21:04 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 [this message]
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

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=20090822210443.GA12033@sewage \
    --to=matthew.garman@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rwheeler@redhat.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).