From: Brad Campbell <lists2009@fnarfbargle.com>
To: "Mathias Burén" <mathias.buren@gmail.com>, dag@newtech.fi
Cc: "Nuno Magalhães" <nunomagalhaes@eu.ipp.pt>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID newbie, 1 vs 5, chunk sizes
Date: Wed, 18 Jun 2014 20:16:16 +0800 [thread overview]
Message-ID: <53A18310.6020900@fnarfbargle.com> (raw)
In-Reply-To: <CADNH=7E+xTPoM4LL_DJrpWxJjsw0aV_w7fVEosu1uc=1dsh16A@mail.gmail.com>
On 18/06/14 19:58, Mathias Burén wrote:
> On 18 June 2014 11:19, Dag Nygren <dag@newtech.fi> wrote:
>> Just love my HGST 4 TB drives. The first ones that haven't
>> developed any pending/remapped sectors during the 9 months
>> they have been in 24/7 use. Previously tried different Seagates, with
>> constant problems (And yes - Had the SCT turned on). Also tested a WD red,
>> but saw similar symptoms developing and so degraded that to a storage
>> disk for my boy...
>> HGST was some 20€ more expensive and hard to get here but definitely
>> worth it.
>>
>
>
> If we're comparing drives, my 8x WD20EARS / EARX have been spinning
> for years. 2 drives just failed after ~3.4 years uptime (24/7) and
> over 400,000 head parkings. They had weekly SMART self-test and
> monthly RAID6 scrubs, and a few unexpected power losses. Good value.
> But YMMV.
My experience has been almost any drive, no matter how naff can be made
to last well by simply keeping them spinning and at a roughly constant
temperature. I generally replace my bulk storage drives at about 4
years. My first lot were Maxtor 250G cheapies and all 12 of them went
for over 4.5 years. My current batch are WD Green 2TB and they all have
~26,000 hours on them. One of my SAS drives has over 49,000 hours on it.
Even a set of cheap Maxtor DiamondMAX 22 1TB drives lasted near enough
to 25,000 hours before I relegated them to an off-line backup machine.
The constant has been keeping them running 24/7 and doing a pretty
thorough burn in to weed out the early life failures.
For example the random WD Green 2T I picked has 26,917 hours and 60
power cycles. Most of those would have been caused over a 12 week period
when I had power issues with the UPS and none would have been off long
enough to noticeably let the drive cool down.
Keep 'em spinning and warm.
--
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:[~2014-06-18 12:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 21:01 RAID newbie, 1 vs 5, chunk sizes Nuno Magalhães
2014-06-14 21:56 ` Stan Hoeppner
2014-06-15 11:50 ` Nuno Magalhães
[not found] ` <pmrj5x4rq3qbl6unnu7guho9.1402849407134@email.android.com>
2014-06-15 17:40 ` Nuno Magalhães
2014-06-16 2:23 ` Phil Turmel
2014-06-16 12:36 ` Nuno Magalhães
2014-06-16 13:19 ` Mark Knecht
2014-06-16 14:28 ` Phil Turmel
2014-06-16 16:14 ` Nuno Magalhães
2014-06-16 20:13 ` Phil Turmel
2014-06-16 21:02 ` Mark Knecht
2014-06-17 0:41 ` Nuno Magalhães
2014-06-17 0:47 ` Brad Campbell
2014-06-17 9:09 ` Nuno Magalhães
2014-06-17 19:50 ` Stan Hoeppner
2014-06-18 2:55 ` Brad Campbell
2014-06-18 7:33 ` Wilson, Jonathan
2014-06-18 10:19 ` Dag Nygren
2014-06-18 11:58 ` Mathias Burén
2014-06-18 12:16 ` Brad Campbell [this message]
2014-06-18 17:34 ` Roman Mamedov
2014-06-19 6:45 ` Wilson, Jonathan
2014-06-29 13:22 ` Nuno Magalhães
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=53A18310.6020900@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=dag@newtech.fi \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=nunomagalhaes@eu.ipp.pt \
/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