From: Bill Davidsen <davidsen@tmr.com>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Fri, 21 Aug 2009 18:00:43 -0400 [thread overview]
Message-ID: <4A8F190B.9010406@tmr.com> (raw)
In-Reply-To: <20090820163522.GA29215@sewage>
Matt Garman wrote:
> The scope of this question is probably broader than Linux RAID, but
> I thought I'd try here before going to the LKML...
>
> I have a fileserver/NAS box that has four Western Digital GreenPower
> drives in software RAID-5 (i.e. Linux md). There was some noise
> about these drives not too long ago: when used under Linux, they
> tend to have really high (and rapidly increasing) SMART
> Load_Cycle_Count values[1].
>
> Basically, in order to save power, these drives park the read/write
> heads after so many seconds of inactivity. According to
> SilentPCReview[2], the 1 TB model uses 5.7W when idle and only 3.7W
> when the heads are unloaded. Apparantly, each head parking event
> causes teh Load_Cycle_Count value to increase.
>
> Most people seek to disable this head parking behavior to stop that
> Load_Cycle_Count value from growing alarmingly high. I actually
> want to use it to it's full potential.
>
> I've got a Kill-A-Watt electricity meter connected to my NAS box. I
> see a difference of 10 watts power usage when the heads park (I can
> hear them unload, so I know when it happens). Allowing for some
> power supply inefficiency, I'd say my observation is consistent with
> SPCR's numbers.
>
> The problem is, the drives don't stay in this parked state very
> long. I haven't actually timed the state changes, but average power
> consumption over a long time (e.g. a week or more) is at the higher
> (i.e. +10) level.
>
> So I figure, something is accessing these drives shortly after the
> heads park, causing them to un-park (and increasing power
> consumption). But this machine is idle 95% of the time. And even
> then, the overwhelming majority of the accesses are reads, with very
> few writes (literally, a handful of writes per week).
>
>
/proc/sys/vm/dirty_expire_centisecs still set to 30 sec?
> 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
> - ???
>
> I'm hoping someone has enough knowledge of these systems to point me
> in the right direction for tuning things. The goal is that when the
> machine is idle, it is "truly" idle, meaning, no disk accesses take
> place and the heads can stay parked (thus saving energy).
>
> Thank you,
> Matt
>
> LINKS:
> [1] http://groups.google.com/group/linux.kernel/browse_thread/thread/505ccf760023d132/7e4f4e996f911efd
>
> [2] http://www.silentpcreview.com/article804-page2.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
"You are disgraced professional losers. And by the way, give us our money back."
- Representative Earl Pomeroy, Democrat of North Dakota
on the A.I.G. executives who were paid bonuses after a federal bailout.
next prev parent reply other threads:[~2009-08-21 22:00 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 [this message]
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=4A8F190B.9010406@tmr.com \
--to=davidsen@tmr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.