From: jahammonds prost <gmitch64@yahoo.com>
To: Jon@eHardcastle.com, "Majed B." <majedb@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Array Power Management
Date: Mon, 7 Sep 2009 07:02:17 -0700 (PDT) [thread overview]
Message-ID: <262927.41980.qm@web55804.mail.re3.yahoo.com> (raw)
In-Reply-To: <342934.45030.qm@web51305.mail.re2.yahoo.com>
> This is interesting.. I have the -S set for all my 6 drives in the array and have for some time and I do not unmount the array - access wakes the drives up - usually most of them, sometimes only a few of them.
I wasn't sure that that would be a safe thing to do, and not finding anything via google, I though it was best to ask. I've also been looking at sdparm, which seems to be more in tune for SATA drives, rather than PATA ones.
> The only part of this that has caused me any problems are scheduled smartd checks - these cause timeout errors.
How are you scheduling the checks? via cron? It's not something I do at the moment, but probably should - I'd rather get some notification that a drive is going to fail, rather than have to deal with a failed one. I'd think about putting an sdparm --command=start /dev/sd[c-p] or whatever to start the disks up before doing a check (and maybe a command=stop when done). I'm guessing that it would be OK to use hdparm to set the spin down timeout, and then sdparm to start the disk spinning again (I can't find an sdparm option to set the timeout)
> In my case, if they are not used for 30mins; they wont be used for several hours.
This is usually the situation I am in as well, certainly my media server... It usually get used for 3 or 4 hours, then nothing much till the next day.
Graham
next prev parent reply other threads:[~2009-09-07 14:02 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 [this message]
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
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=262927.41980.qm@web55804.mail.re3.yahoo.com \
--to=gmitch64@yahoo.com \
--cc=Jon@eHardcastle.com \
--cc=linux-raid@vger.kernel.org \
--cc=majedb@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 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).