linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Garman <matthew.garman@gmail.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Array Power Management
Date: Thu, 10 Sep 2009 11:51:56 -0500	[thread overview]
Message-ID: <20090910165156.GA30820@sewage> (raw)
In-Reply-To: <292245.77763.qm@web55804.mail.re3.yahoo.com>

On Sun, Sep 06, 2009 at 08:48:03PM -0700, jahammonds prost wrote:
> I can do this on single drives using hdparm -S to set the spindown
> timeout, and the disks will spin up on activity as needed. Is
> there something similar I can do with an md array? I can see
> there's a /sys/block/md0/power/wakeup file, but I can't seem to
> find any documentation on it. I have thought about doing an hdparm
> -S on the array disks, but I suspect that would be A Bad Thing
> (tm).

On the same note, does anyone have any thoughts on the wear-and-tear
caused by frequent spinup/spindown cycles?

My fileserver has the Western Digital RE2 "enterprise" grade drives.
I remember reading (years ago) that, in general, "enterprise" grade
drives were designed to be always running (think 24/7 server), and
rarely spun down.  As such, they did not tolerate a "consumer
desktop" usage pattern very well, and trying to save power in this
way would actually cause them to fail prematurely.

Is/was such a thing true?  Is it worth worrying about?

Thanks,
Matt


  parent reply	other threads:[~2009-09-10 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07  3:48 Array Power Management jahammonds prost
2009-09-07  9:57 ` Majed B.
2009-09-07 10:19   ` Jon Hardcastle
2009-09-07 14:02     ` jahammonds prost
2009-09-07 14:05       ` Majed B.
2009-09-07 12:55   ` Tapani Tarvainen
2009-09-07 13:37     ` jahammonds prost
2009-09-10 16:51 ` Matt Garman [this message]
2009-09-11 12:27   ` Ryan Wagoner

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=20090910165156.GA30820@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).