From: Neil Brown <neilb@suse.de>
To: "Patrick Ale" <patrick.ale@gmail.com>
Cc: "Michael-Luke Jones" <jonesml@fastmail.to>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [QUESTION] Sata RAID
Date: Mon, 26 Feb 2007 19:37:37 +1100 [thread overview]
Message-ID: <17890.40017.353353.633027@notabene.brown> (raw)
In-Reply-To: message from Patrick Ale on Monday February 26
On Monday February 26, patrick.ale@gmail.com wrote:
> On 2/24/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> > On 2/24/07, Michael-Luke Jones <jonesml@fastmail.to> wrote:
>
> One more question regarding this, I am aware its not *really* kernel
> related but answering this question now will save yourself a lot of
> bogus emails from me about MD oopses later and all, and I want to
> setup my disks right once and for all and never witness what I
> witnessed last weeks with my ATA disks.
>
> Would you use MD at all, taking in account the disks come from the
> same batch and all? I hear these things about MD/RAID being pointless
> when you use disks from the same brand/type/batch since they most
> likely will break shortly after eachother.
Well, it the drives break shortly after each other, you lose your data
no matter what is happening.
But if it is just occasional read errors, md/raid handles those quite
well these days, over-writing the bad block with correct data.
Of course write error cause the drive to be kicked from the array, but
a write error on a modern drive means something much worse that a bit
of bad media has happened.
If I wanted raid1/5/6 I would certainly use md no-matter what batch
the drives were from (but maybe I am a tiny bit biased).
NeilBrown
next prev parent reply other threads:[~2007-02-26 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 10:10 Patrick Ale
2007-02-24 15:24 ` Bartlomiej Zolnierkiewicz
2007-02-24 17:11 ` Michael-Luke Jones
2007-02-24 17:19 ` Patrick Ale
2007-02-26 8:30 ` Patrick Ale
2007-02-26 8:37 ` Neil Brown [this message]
2007-02-28 1:51 ` Bill Davidsen
2007-02-28 13:02 ` Alan
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=17890.40017.353353.633027@notabene.brown \
--to=neilb@suse.de \
--cc=jonesml@fastmail.to \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.ale@gmail.com \
/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
Powered by JetHome