From: Brad Campbell <lists2009@fnarfbargle.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: question about the best suited RAID level/layout
Date: Fri, 05 Jul 2013 09:07:36 +0800 [thread overview]
Message-ID: <51D61C58.2020207@fnarfbargle.com> (raw)
In-Reply-To: <1372978687.5249.52.camel@fermat.scientia.net>
On 05/07/13 06:58, Christoph Anton Mitterer wrote:
> I'd have even one more question here: Has anyone experience with my idea
> of intentionally running devices of different vendors (Seagate, WD,
> HGST)... for resilience reasons?... Does it work out as I plan, or are
> there any hidden caveats I can't see which make the resilience (not the
> performance) worse?
I've got both here. A large RAID-6 comprised entirely of single brand,
single type consumer drives and a smaller RAID-10 built from a diverse
selection. Both have had great reliability, so that's not really a good
data point for you.
What I *have* found over the years is the importance of weeding out
early failures. Before I commit a disk to service, I subject it to a
couple of weeks of hard work. I usually knock up a quick and dirty bash
script with multiple concurrent instances of dd reading and writing to
differing parts of the disk simultaneously, with a bonnie++ run for good
measure. With all this going on at the same time the drive mechanism
gets a serious workout and the drive stays warmer than it will in actual
service. If I have the chance, I do all the drives simultaneously and
preferably in the machine they are going to spend the next couple of
years. If I can't do that, then I have a burn-in chassis built from a
retired server that can do 15 at a time.
This has proven quite effective in spotting the early life failures. I
generally find (for consumer drives) if they pass this they'll last the
3 years of 24/7 I use them for before I replace them. My enterprise
drives are a different story, and I have some here with just over 38k
hours on them. I'll probably replace them for bigger drives before they
ever fail.
Regards,
Brad
next prev parent reply other threads:[~2013-07-05 1:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 18:17 question about the best suited RAID level/layout Christoph Anton Mitterer
2013-07-04 21:43 ` Phil Turmel
2013-07-04 22:58 ` Christoph Anton Mitterer
2013-07-05 1:07 ` Brad Campbell [this message]
2013-07-06 0:36 ` Christoph Anton Mitterer
2013-07-06 5:29 ` Brad Campbell
2013-07-06 14:49 ` Christoph Anton Mitterer
2013-07-07 6:36 ` Brad Campbell
2013-07-06 7:40 ` Piergiorgio Sartor
2013-07-06 14:52 ` Christoph Anton Mitterer
2013-07-05 1:12 ` Stan Hoeppner
2013-07-06 0:46 ` Christoph Anton Mitterer
2013-07-06 8:36 ` Stan Hoeppner
2013-07-06 15:04 ` Christoph Anton Mitterer
2013-07-06 15:41 ` Matt Garman
2013-07-07 14:08 ` David Brown
2013-07-07 16:45 ` Stan Hoeppner
2013-07-07 17:26 ` Christoph Anton Mitterer
2013-07-09 15:50 ` Stan Hoeppner
2013-07-05 13:36 ` Phil Turmel
2013-07-06 1:11 ` Christoph Anton Mitterer
2013-07-06 2:19 ` Phil Turmel
2013-07-06 17:55 ` Christoph Anton Mitterer
2013-07-07 12:46 ` Bernd Schubert
2013-07-07 17:39 ` Christoph Anton Mitterer
2013-07-05 11:10 ` David Brown
2013-07-06 0:55 ` Christoph Anton Mitterer
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=51D61C58.2020207@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=calestyo@scientia.net \
--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.