<p dir="ltr">Enterprise class SATA and SAS drives typically still have a 5 year warranty.</p>
<div class="gmail_quote">On Feb 12, 2014 7:04 PM, "JD" <<a href="mailto:jdp@algoloma.com">jdp@algoloma.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/12/2014 06:43 PM, Ray Vastly wrote:<br>
> Why should you avoid raid 5 or 6 when using large hard disks? What Raid<br>
> configuration would you recommend for 12 HDDs each 2 TB in a NAS?<br>
<br>
My personal opinion?<br>
<br>
Backups, then<br>
RAID10, then<br>
RAIDz2, then<br>
RAID1, then<br>
RAIDz<br>
<br>
A few years ago, it was believed that large drives had an issue with MTBF such<br>
that it was likely that after replacing a failed HDD another drive would fail<br>
during the RAID-rebuild. I haven't seen anything recent to prove or disprove it.<br>
I do know that drive warranties have changed from 5 yrs, to 3 yrs to 1 yr over<br>
the same period. Many USB drives people buy to backup stuff at home have 90 day<br>
warranties. Buyer beware.<br>
<br>
When I upgraded from 4x320G RAID5 to 4x2TB disks, I switched to RAID1. I still<br>
do weekly RAID scrubs and nightly backups. I'd never experienced the<br>
RAID5-hole, but didn't want to either.<br>
<br>
BTW, 1 of those 2TB disks failed last week after 16 months in-service.<br>
<br>
<br>
><br>
> On Feb 12, 2014 6:40 PM, "Jeff Hubbs" <<a href="mailto:jhubbslist@att.net">jhubbslist@att.net</a><br>
> <mailto:<a href="mailto:jhubbslist@att.net">jhubbslist@att.net</a>>> wrote:<br>
><br>
> On 2/12/14, 5:00 PM, Lightner, Jeff wrote:<br>
>> <snip>____<br>
>><br>
>> __ __<br>
>><br>
>> You really should be using RAID6 or RAID10 rather than RAID5 as it is even<br>
>> more redundant (i.e. can survive 2 disks failures).<br>
>><br>
> And you shouldn't be using RAID5 or RAID6 at all if your drives are<br>
> 750-1000GB or larger.<br>
><br>
> Mail and database servers would be two good places to make use of<br>
> snapshotting filesystems. Note that some email systems that use message<br>
> stores go insane if the message store is not in the state that the rest of<br>
> the email system presumes it's in, so you have to make sure that your<br>
> backup/recovery scheme doesn't capture messages and message metadata/index<br>
> in different states.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a> <mailto:<a href="mailto:Ale@ale.org">Ale@ale.org</a>><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
<br>
<br>
--<br>
JD Pflugrath<br>
Value | Results<br>
Direct: +001.678.685.8882<br>
Ofc: <a href="tel:1.866.963.2546" value="+18669632546">1.866.963.2546</a><br>
Managing Director<br>
Algoloma Systems, LLC<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>