From: Phil Turmel <philip@turmel.org>
To: Roman Mamedov <rm@romanrm.ru>
Cc: "Gavin Flower" <gavinflower@yahoo.com>,
"Mathias Burén" <mathias.buren@gmail.com>,
neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive
Date: Thu, 28 Apr 2011 18:11:12 -0400 [thread overview]
Message-ID: <4DB9E600.6040508@turmel.org> (raw)
In-Reply-To: <20110429021118.0f247326@natsu>
On 04/28/2011 04:11 PM, Roman Mamedov wrote:
> On Thu, 28 Apr 2011 13:03:39 -0700 (PDT)
> Gavin Flower <gavinflower@yahoo.com> wrote:
>
>> A couple of days ago, my friend Mario brought over his oscilloscope and a
>> volt meter. The 5 volt rail was showing about 4.7 volts, typically it
>> should be 5.2 - 5.4 (from memory of what he said), and the voltage looked
>> shaky on the oscilloscope. The old power supply rated at 400 Watts.
>
> 4.7V is fine, those voltages have a tolerance of +/-10%. And if you have a
> deviation there, it is actually better for it to be to the lower side, than
> equivalent to the higher. Reason: no heat increase.
Uh. Close, but no.
Quoting the Seagate manual for that drive:
> 2.7.3 Voltage tolerance
>
> Voltage tolerance (including noise):
> 5V +10% / -7.5%
> 12V +10% / -10.0%
So he was somewhere around 75mV above the low spec, and it was "shaky". If his meter was rounding up to 4.7 from 4.65, he could have been as close as 25mV to the low spec.
Based on the manual, the best noise tolerance will be at 5.0625V, the middle of the spec.
There might be big datacenter engineers that'll trade some noise margin for heat dissipation savings. For that drive's active power consumption, a 5% voltage reduction (half of his noise margin) will save him, at most, 28W (5 drives * 6.19W * 0.95^2). That's a savings of $14 per year for 24/7/365 usage in my household.
I'd spend the $14 for the safety margin on *my* data. (And I do.)
Regards,
Phil
next prev parent reply other threads:[~2011-04-28 22:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 22:24 RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive Gavin Flower
2011-04-13 22:28 ` Mathias Burén
2011-04-14 0:15 ` Gavin Flower
2011-04-14 4:08 ` Roman Mamedov
2011-04-14 13:16 ` Phil Turmel
2011-04-14 21:12 ` Gavin Flower
2011-04-14 22:23 ` Phil Turmel
2011-04-28 20:03 ` Gavin Flower
2011-04-28 20:11 ` Roman Mamedov
2011-04-28 22:11 ` Phil Turmel [this message]
2011-04-28 22:40 ` Phil Turmel
2011-04-13 23:09 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2011-04-14 21:14 Gavin Flower
2011-04-14 21:19 ` Mathias Burén
2011-04-14 23:15 ` John Robinson
2011-04-08 2:01 Gavin Flower
2011-04-08 1:34 Gavin Flower
2011-04-08 1:32 Gavin Flower
2011-04-08 9:34 ` NeilBrown
2011-04-08 9:59 ` Gavin Flower
2011-04-08 11:50 ` NeilBrown
2011-04-11 6:50 ` Gavin Flower
2011-04-12 21:30 ` Gavin Flower
2011-04-13 10:57 ` John Robinson
2011-04-13 11:13 ` NeilBrown
2011-04-13 11:58 ` John Robinson
2011-04-13 20:30 ` Gavin Flower
2011-04-07 21:58 Gavin Flower
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=4DB9E600.6040508@turmel.org \
--to=philip@turmel.org \
--cc=gavinflower@yahoo.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=neilb@suse.de \
--cc=rm@romanrm.ru \
/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).