From: Joachim Otahal <Jou@gmx.net>
To: Aryeh Gregor <Simetrical+list@gmail.com>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
linux-raid@vger.kernel.org
Subject: Re: RAID Class Drives`
Date: Fri, 19 Mar 2010 19:14:50 +0100 [thread overview]
Message-ID: <4BA3BF1A.2060905@gmx.net> (raw)
In-Reply-To: <7c2a12e21003190943t546ade49u2294310ed7d9921e@mail.gmail.com>
Aryeh Gregor schrieb:
> On Fri, Mar 19, 2010 at 4:15 AM, John Robinson
> <john.robinson@anonymous.org.uk> wrote:
>
>> Do you have a reference for this? Most drives' operating temperature range
>> is specified up to 55°C, sometimes higher for enterprise drives, without any
>> indication (apart from common sense perhaps) that running them this hot
>> reduces lifespan.
>>
> Google's study of>100,000 disks over 9 months or so
> <http://labs.google.com/papers/disk_failures.html> suggests that
> hotter drives don't fail much more often:
>
Thanks for the link.
That study was referred to as a comparison to the current situation. But
google only tested up to 400 GB in that statistic, and I DO remember
that my old 160GB to 500 GB drives were all a lot hotter than any of my
current drives. Those Samsung 1TB drives only reached 35°C during last
hot summer, but I did let the fan rotate faster during the summer.
Current real world data of my drives (Windows main machine, room
temperature is 23°C right now):
SAMSUNG 1 TB 27°C (HD103UJ)
WD 1 TB 30°C (WD10 EACS-00ZJBO)
WD 750 GB 34°C (WD75 00AACS-00ZJBO)
SAMSUNG 1 TB 25°C (HD103UJ)
Linux Server (mirrored drives):
SEAGATE 1,5 TB 34°C (ST31500341AS)
SEAGATE 1,5 TB 34°C (ST31500341AS) <- this one will probably fail in one
or one and a half year if the realloc-sector count continues to develop
this way.
Joachim Otahal
--
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
next prev parent reply other threads:[~2010-03-19 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 13:48 RAID Class Drives` Randy Terbush
2010-03-18 16:45 ` Joachim Otahal
2010-03-19 8:15 ` John Robinson
2010-03-19 16:43 ` Aryeh Gregor
2010-03-19 16:53 ` Mattias Wadenstein
2010-03-19 18:14 ` Joachim Otahal [this message]
2010-03-22 6:55 ` Leslie Rhorer
2010-03-22 16:29 ` Eric Shubert
2010-03-23 1:23 ` Brad Campbell
2010-03-23 17:45 ` Eric Shubert
2010-04-02 5:43 ` Leslie Rhorer
2010-04-02 20:04 ` Richard Scobie
2010-04-05 2:50 ` Leslie Rhorer
2010-03-19 17:53 ` Joachim Otahal
2010-03-20 17:26 ` Bill Davidsen
2010-03-21 16:14 ` Eric Shubert
2010-03-18 19:43 ` Randy Terbush
2010-04-18 12:11 ` CoolCold
[not found] ` <4BCB6484.7040500@stud.tu-ilmenau.de>
2010-04-19 10:11 ` CoolCold
[not found] ` <4BCC7C27.1000606@stud.tu-ilmenau.de>
2010-04-19 20:10 ` CoolCold
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=4BA3BF1A.2060905@gmx.net \
--to=jou@gmx.net \
--cc=Simetrical+list@gmail.com \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
/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.