linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Adamski <k@adamski.org>
To: Mattias Wadenstein <maswan@acc.umu.se>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
	Jeremy Thompson <jeremythompson82@gmail.com>,
	Brad Campbell <brad@fnarfbargle.com>, Asdo <asdo@shiftmail.org>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: It is safe to stop Raid being reshaped
Date: Fri, 30 Dec 2011 09:51:25 -0500	[thread overview]
Message-ID: <1325256685.7358.34.camel@oxygen.netxsys.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1112301310190.24961@montezuma.acc.umu.se>

On Fri, 2011-12-30 at 13:16 +0100, Mattias Wadenstein wrote:
> On Fri, 30 Dec 2011, Mikael Abrahamsson wrote:
> 
> > On Thu, 29 Dec 2011, Jeremy Thompson wrote:
> >
> >> I thought about this as well - I have an Enermax 450 in there right now... 
> >> I'll have to look for a higher watt power supply next I guess.
> >
> > Also look at how your feeds are balanced. Some PSUs have two rails, putting 
> > all drives on a single rail causes your load handling capacity to go down 
> > significantly. I recommend getting a single rail PSU as well, well above the 
> > capacity you think you need.
> 
> Not only that, take a good look at both the 5V and 12V specs, and compare 
> them to the draw needed by the drives (and the rest of the system). I've 
> found that the ammount of 5V available varies lots between PSUs, without 
> much correlation with the 12V supply. Which is fine for modern CPUs/GPUs 
> which mostly uses 12V, but drives seem to want quite a bit of 5V too.
> 
> One other common problem with multiple rail PSUs is that often all the 
> useful power connectors (sata/molex) are only on one rail. I wouldn't mind 
> multiple rails if I could actually use all of them for drives.
> 
> For the 24-drive home build I've done, I've actually ended up running two 
> PSUs in parallel (joining ground), but this is hardly something to 
> recommend to anyone sane. ;)

I can give you my recommendation for a power supply based on my box.
The box has 22 drives (all 7200), dual core Phenom II, 8 Gig ram.
The PS is a OCZ ModXstream Pro 700. It has been running for over a year
without showing any problems. In a normal steady state the box draws 260
Watts from the wall as measures by a Kill-A-Watt device.

K


      reply	other threads:[~2011-12-30 14:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 17:55 It is safe to stop Raid being reshaped Jeremy Thompson
2011-12-28 18:15 ` Gordon Henderson
2011-12-28 19:02 ` Asdo
2011-12-28 19:06   ` Jeremy Thompson
2011-12-29  2:02     ` Asdo
2011-12-29  2:23       ` Jeremy Thompson
2011-12-29 11:21         ` Gordon Henderson
2011-12-29 23:35         ` Brad Campbell
2011-12-29 23:37           ` Jeremy Thompson
2011-12-30  4:31             ` Mikael Abrahamsson
2011-12-30  4:31               ` Jeremy Thompson
2011-12-30  6:19               ` Brad Campbell
2011-12-30 12:16               ` Mattias Wadenstein
2011-12-30 14:51                 ` Krzysztof Adamski [this message]

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=1325256685.7358.34.camel@oxygen.netxsys.com \
    --to=k@adamski.org \
    --cc=asdo@shiftmail.org \
    --cc=brad@fnarfbargle.com \
    --cc=jeremythompson82@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=maswan@acc.umu.se \
    --cc=swmike@swm.pp.se \
    /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).