From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-f52.google.com ([209.85.219.52]:40296 "EHLO mail-oa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750827Ab3KUCqE (ORCPT ); Wed, 20 Nov 2013 21:46:04 -0500 MIME-Version: 1.0 In-Reply-To: <528D61C5.70902@hardwarefreak.com> References: <528A90B7.5010905@zytor.com> <528AA1EB.3010909@zytor.com> <528BCA2D.5010500@redhat.com> <73BEB41F-0FAC-4108-BEA9-DB6D921F6F55@cs.utk.edu> <528D61C5.70902@hardwarefreak.com> Date: Wed, 20 Nov 2013 18:46:03 -0800 Message-ID: Subject: Re: Triple parity and beyond From: John Williams To: stan@hardwarefreak.com Cc: James Plank , Ric Wheeler , Andrea Mazzoleni , "H. Peter Anvin" , Linux RAID Mailing List , Btrfs BTRFS , David Brown , David Smith Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-btrfs-owner@vger.kernel.org List-ID: For myself or any machines I managed for work that do not need high IOPS, I would definitely choose triple- or quad-parity over RAID 51 or similar schemes with arrays of 16 - 32 drives. No need to go into detail here on a subject Adam Leventhal has already covered in detail in an article "Triple-Parity RAID and Beyond" which seems to match the subject of this thread quite nicely: http://queue.acm.org/detail.cfm?id=1670144