From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I power disk off?
Date: Thu, 6 Oct 2011 15:49:57 -0500 [thread overview]
Message-ID: <CAEH5T2M1PfPt-2-5sPaWnKELMAS_6sGQiY7PZ3Q79UnCu=dqHg@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+eeR8V8fyUazX973HFdx9hsZFKv1F60GHTWy88HzWGyhEA@mail.gmail.com>
On Thu, Oct 6, 2011 at 3:21 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Thu, Oct 6, 2011 at 1:03 PM, Paul Hartman
> <paul.hartman+gentoo@gmail.com> wrote:
>> On Thu, Oct 6, 2011 at 2:44 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>> Paul,
>>> Would hdparm be advisable if the drive was part of a RAID? I suspect not.
>>>
>>> I don't think this applies to the OP but for the sake of discussion
>>> why not include RAID as part of the solution, if possible.
>>
>> I use hdparm to set power-saving on all members of my RAID5 and it
>> works (in my case, I'm setting them to never spin-down). I created a
>> file /etc/local.d/hd-power-level-fix.start containing one line:
>>
>> hdparm -B 254 /dev/sd[abcdef]
>>
>> which automatically sets those drives to never spin down.
>>
>> In my original recommendation, I hadn't considered hdparm's "spindown
>> immediately" option. I was thinking of the -B command like I used
>> above, to adjust the "spin down after X idle time" option. If all
>> members of the RAID have the same idle time they'll probably all spin
>> up and down together under normal usage (well, depending what kind of
>> RAID it is, I suppose). In my case, I found the "click, whirr, click,
>> whirr, click, whirr, click, whirr, click, whirr" waiting for 5 disks
>> to spin-up when I accessed the RAID annoying, so I disabled it. (I
>> have not done any power-consumption measurements to see what that's
>> costing me...)
>>
>
> My worry was that if the mdraid daemon saw one drive gone - either
> when starting to spin down or when one spins up slowly - and if mdraid
> didn't understand that all this stuff was taking place intentionally
> then it might mark that drive as having failed.
>
> I can see the utility of spinning down a RAID in something like a home
> video server where I keep movies. The machine could be on, ready to
> serve a movie, but the drives aren't drawing much power.
>
> I suspect that there's a pretty substantial power savings on a big
> RAID if done right, but I haven't done any measurements either.
The drive's not gone, it's not offline, it's just not spinning. I
don't think mdraid would even know that.
next prev parent reply other threads:[~2011-10-06 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 19:14 [gentoo-user] How can I power disk off? Jarry
2011-10-06 19:27 ` Mark Knecht
2011-10-06 19:34 ` Alex Schuster
2011-10-06 19:38 ` Paul Hartman
2011-10-06 19:44 ` Mark Knecht
2011-10-06 20:03 ` Paul Hartman
2011-10-06 20:21 ` Mark Knecht
2011-10-06 20:28 ` Michael Mol
2011-10-07 1:04 ` Mark Knecht
2011-10-07 1:14 ` Michael Mol
2011-10-07 13:19 ` Mark Knecht
2011-10-06 20:31 ` David W Noon
2011-10-06 20:56 ` Paul Hartman
2011-10-06 20:49 ` Paul Hartman [this message]
2011-10-06 19:41 ` Dale
2011-10-07 1:29 ` [gentoo-user] " Grant Edwards
2011-10-07 2:51 ` Paul Hartman
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='CAEH5T2M1PfPt-2-5sPaWnKELMAS_6sGQiY7PZ3Q79UnCu=dqHg@mail.gmail.com' \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.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