lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Feb 2007 19:37:37 +1100
From:	Neil Brown <neilb@...e.de>
To:	"Patrick Ale" <patrick.ale@...il.com>
Cc:	"Michael-Luke Jones" <jonesml@...tmail.to>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [QUESTION] Sata RAID

On Monday February 26, patrick.ale@...il.com wrote:
> On 2/24/07, Patrick Ale <patrick.ale@...il.com> wrote:
> > On 2/24/07, Michael-Luke Jones <jonesml@...tmail.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ