All of lore.kernel.org
 help / color / mirror / Atom feed
From: <brian.foster@emc.com>
To: piergiorgio.sartor@nexgo.de, roberto@spadim.com.br
Cc: linux-raid@vger.kernel.org
Subject: RE: RAID HDDs spin up sequence
Date: Tue, 1 Feb 2011 08:55:41 -0500	[thread overview]
Message-ID: <9EBB77E762A6744BACE68EDD6A4796990129EC0E@MX31A.corp.emc.com> (raw)
In-Reply-To: <20110131222348.GA15912@lazy.lzy>

> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
> owner@vger.kernel.org] On Behalf Of Piergiorgio Sartor
> Sent: Monday, January 31, 2011 5:24 PM
> To: Roberto Spadim
> Cc: Piergiorgio Sartor; linux-raid@vger.kernel.org
> Subject: Re: RAID HDDs spin up sequence
> 
> On Mon, Jan 31, 2011 at 07:09:24PM -0200, Roberto Spadim wrote:
> > you psu must be dimensioned to work with everythink at full work load
> > (it´s a real production NAS right?! not a test)
> > your SAS/IDE/SATA controller and HDD manual should be checked
> > how hdd wake up? one command (read/write) over sata/sas/ide channel
> wake it up?
> > on linux raid we have a read algorithm and a write algorithm
> > if a raid1 write occur all disks will wake up
> > if a raid1 (raid0 or another) read occur only the disk will wake up
> >
> > but check you SATA/IDE/SATA controller, how it wake up your disk, and
> > how you hdd wake up
> 
> Hi, thanks for the answer, unfortunately I was
> hoping to have made myself clear enough.
> 
> First of all, it is a RAID-6, so let's say that's
> already decided by requirements. With SATA HDDs.
> 
> Second, the question was exactly about how the HDDs
> are waked up. This is a SW issue, trying with normal
> setups, i.e. a couple of disks, it is possible to
> send them to sleep (hdparm -y /dev/hdX) and the wake
> them up by a simple access.
> I had no opportunity to check this with a RAID-5/6,
> so I was asking if anyone knows.
> 
> Finally, in order to be power efficient, the PSU,
> assuming something like an 80 Plus Gold, should work
> at not less than 20% of the nominal power, otherwise
> (according to some reviews), the efficiency drops far
> below the 80%~90% declared by the 80 Plus standard
> (which is measured at 20%, 50% and 100% of the maximum
> specified power).
> It seem it gets easily around 40%~50%.
> So, the PSU must be somehow under dimensioned for the
> spin up of 10 HDDs, which seem to require a possible
> 30W*10=300W (some nasty HDDs seem to require 30W, in
> this situation) only for the storage.
> 
> If the HDDs spin up one after the other, then the peak
> consumption is only 30W, which might allow a lower
> power PSU, in contrast with the requirement to provide
> 300W alone for the spin up.
> 
> So, back to the original question, if a 10 HDDs RAID-6
> is in standby, how do the single HDD will be waked up,
> in case of access? Of course, a quite larger access,
> i.e. some GiB of data.

We have a similar situation with our Iomega NAS products. We had a fairly crude locking mechanism implemented at the SCSI level that suits our needs to support staggered spin up. As indicated previously, we find that a 1 or 2 second delay between spin ups modulates the current draw enough such that we don't run into problems. We use this in conjunction with MD without much of a problem.

I'm not sure that the code as implemented is appropriate for mainline inclusion (and I'm not going to post it directly), but FYI the patches are included in the open source tarball that is made available on the support section of the iomega.com website (hint: check out the ix12 support & downloads section).

Brian

> 
> Thanks again,
> 
> bye,
> 
> --
> 
> piergiorgio
> --
> 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

--
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

  parent reply	other threads:[~2011-02-01 13:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 20:18 RAID HDDs spin up sequence Piergiorgio Sartor
2011-01-31 21:09 ` Roberto Spadim
2011-01-31 21:10   ` Roberto Spadim
2011-01-31 21:11   ` Mathias Burén
2011-01-31 21:25     ` Roberto Spadim
2011-01-31 21:29       ` Mathias Burén
2011-01-31 21:35         ` Roberto Spadim
2011-01-31 22:23   ` Piergiorgio Sartor
2011-01-31 22:42     ` Roberto Spadim
2011-01-31 22:42       ` Roberto Spadim
2011-01-31 23:07       ` Piergiorgio Sartor
2011-01-31 23:12         ` Roberto Spadim
2011-02-01  1:45         ` Phillip Susi
2011-02-01 12:39           ` Roman Mamedov
2011-02-01 13:10           ` John Robinson
2011-02-01 21:37             ` Stan Hoeppner
2011-02-01 22:46               ` Roberto Spadim
2011-02-01 13:55     ` brian.foster [this message]
2011-02-01 14:37       ` Roberto Spadim
2011-02-01 14:44         ` Roberto Spadim
2011-02-01 15:01           ` John Robinson
2011-02-01 15:46             ` Roberto Spadim

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=9EBB77E762A6744BACE68EDD6A4796990129EC0E@MX31A.corp.emc.com \
    --to=brian.foster@emc.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=piergiorgio.sartor@nexgo.de \
    --cc=roberto@spadim.com.br \
    /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.