From: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Wed, 26 Aug 2009 14:45:21 -0500 [thread overview]
Message-ID: <20090826194521.GB27854@sewage> (raw)
In-Reply-To: <20090822210443.GA12033@sewage>
On Sat, Aug 22, 2009 at 04:04:43PM -0500, Matt Garman wrote:
> 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.
This is correct. One thing I noticed yesterday, when I was running
blktrace and having block_dump enabled: the heads *never* parked
during this time. Even though I had zero accesses on the data
drives, the system drive was getting hit pretty heavily (because I
deliberately had syslog write the block_dump stuff). When I finally
stopped all the heavy logging, I ran "sync" and noticed that a few
seconds later, the heads parked.
Almost exactly five minutes later, the heads un-parked.
I repeated: I ran the "sync" command, the heads unloaded, five
minutes later, they re-loaded. I repeated this exactly several
times.
So I re-enabled block_dump (i.e. "echo 1 > /proc/sys/vm/block_dump"),
but disabled syslog (so the system drive wouldn't be thrashed). I
ran the "sync, then wait five minutes test": pdflush and kjournald
apparently caused the wakeup after five minutes.
I set my system drive to ext2 (instead of ext3) in /etc/fstab and
rebooted. I was under the impression that using ext2 instead of
ext3 would eliminate the need for kjournald, but this doesn't appear
to be the case.
So, based on what I've seen so far, there's some "five minute thing"
going on that involves pdflush and/or kjournald.
-Matt
next prev parent reply other threads:[~2009-08-26 19:45 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 [this message]
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=20090826194521.GB27854@sewage \
--to=matthew.garman@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).