From: Goswin von Brederlow <goswin-v-b@web.de>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: If your using large Sata drives in raid 5/6 ....
Date: Wed, 03 Feb 2010 12:25:16 +0100 [thread overview]
Message-ID: <87zl3qv9wj.fsf@frosties.localdomain> (raw)
In-Reply-To: <87f94c371002021446y38dce6fds6acca2b4919ad773@mail.gmail.com> (Greg Freemyer's message of "Tue, 2 Feb 2010 17:46:25 -0500")
Greg Freemyer <greg.freemyer@gmail.com> writes:
> All,
>
> I think the below is accurate, but please cmiiw or misunderstand.
>
> ===
> If your using normal big drives (1TB, etc.) in a raid-5 array, the
> general consensus of this list is that it is a bad idea. The reason being
> that the sector error rate for a bad sector has not changed with
> increasing density.
>
> So in the days of 1GB drives, the likelihood of a undetected /
> repaired bad sector was actually pretty low for the drive as whole.
> But for today's 1TB drives, the odds are 1000x worse. ie. 1000x more
> sectors with the same basic failure rate per sector.
I just had such a case yesterday. It does happen too often. Esspecialy
as drives get older. Rebuilding a raid5 becomes more and more dangerous
as you increase drive capacity.
> So a raid-5 composed of 1TB drives is 1000x more likely to be unable
> to rebuild itself after a drive failure than a raid-5 built from 1 GB
> drives of yesteryear. Thus the current recommendation is to use raid
> 6 with high density drives.
If you can spare the drive and cpu then raid6 is definetly preferable.
Although I think the only future is in combining the raid and filesystem
into one. If you have some corrupted blocks then the FS can tell you
which files are corrupted. Raid only really covers the case of a whole
drive failing well.
MfG
Goswin
--
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-02-03 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87f94c371002021440o3b30414bk3a7ccf9d2fa9b8af@mail.gmail.com>
2010-02-02 22:46 ` If your using large Sata drives in raid 5/6 Greg Freemyer
2010-02-03 9:27 ` Steven Haigh
2010-02-03 10:56 ` Mikael Abrahamsson
2010-02-03 12:24 ` Goswin von Brederlow
2010-02-03 11:25 ` Goswin von Brederlow [this message]
2010-02-03 14:08 ` John Robinson
2010-02-05 15:38 ` Bill Davidsen
2010-02-05 16:14 ` Greg Freemyer
2010-02-05 17:12 ` Bill Davidsen
2010-02-05 16:59 ` John Robinson
2010-02-05 17:40 ` 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=87zl3qv9wj.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=greg.freemyer@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox