public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org,
	smartmontools-support@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Have the velociraptors in a test system now, checkout the errors.
Date: Sun, 07 Dec 2008 02:22:10 +0300	[thread overview]
Message-ID: <493B0922.2080606@msgid.tls.msk.ru> (raw)
In-Reply-To: <alpine.DEB.1.10.0812060709280.8516@p34.internal.lan>

Justin Piszcz wrote:

[big skip..]
> Very interesting story there, what OS(') were you using at the time?
> Windows? Linux? UNIX?

It is linux.  Since 2.2 or 2.0, I don't remember for sure.
With software raid since the day one (was an external patch
in a few first years).

> As far the PSU, just btw/FYI, Velociraptors consume ~4-5 watts a piece,
> my entire system used ~100-120watts with all 12 velociraptors on a 650
> watt PSU (now moved into a test system).

Well.  Others already commented on this, -- different rail can draw
different max power.  But it's a bit more complex still.  Those 4..5
watts is a sustained power consumption, not peak.  When moving heads,
starting/stopping the motor etc, the drive briefly consumes much more
power.  From my choice of cheap PSUs, not all of them can do the work
even when theoretical load is below the capacity.  I.e., the voltage
becomes.. unstable (insufficient filtering/capacitors, bad output
cirquits, too thin wires etc yadda).  And some parts of the system
may "translate" those instabilities into ones and zeros..

It's more: when the drives are in some RAID configuration (esp. raid1
and the like), usually more than one drive works in parallel, at exactly
the same moment (think writes to a raid1).  So it is more possible to
have bad results in raid config than without...

But again: I'm not at all suggesting your problem is in PSU.  It
*might* be here, but I hope your PSU can do the work fine.  And
in my case there were other failures too, more "mysterious".

And by the way, some modern PSUs, especially more powerful ones,
has more than one separate rails for 12v and sometimes 5v.  I.e.
two or more independent (to some extent anyway) 12v circuits.
With obvious advantages.

/mjt

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2008-12-06 23:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06  9:51 Have the velociraptors in a test system now, checkout the errors Justin Piszcz
2008-12-06 11:13 ` Michael Tokarev
2008-12-06 12:11   ` Justin Piszcz
2008-12-06 20:55     ` Kyle Moffett
2008-12-06 23:22     ` Michael Tokarev [this message]
2008-12-11  0:11 ` Bill Davidsen
2008-12-14  3:28   ` Redeeman
2008-12-14  9:05     ` Justin Piszcz
2008-12-17 20:43     ` Bill Davidsen
2008-12-17 23:21       ` Justin Piszcz
2008-12-18 23:14         ` Bill Davidsen

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=493B0922.2080606@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    --cc=xfs@oss.sgi.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