From mboxrd@z Thu Jan 1 00:00:00 1970 From: Piergiorgio Sartor Subject: Re: Is this enough for us to have triple-parity RAID? Date: Sat, 21 Apr 2012 13:18:48 +0200 Message-ID: <20120421111848.GA28576@lazy.lzy> References: <4F8DD02F.1060504@westcontrol.com> <4F905690.3060301@zytor.com> <067e21e2-6f21-48a7-93a8-bb2249534155@email.android.com> <4F91B1C4.5080205@hesbynett.no> <20120420210106.GA2432@lazy.lzy> <20369.54567.60804.896644@tree.ty.sabi.co.UK> <20120420223138.GA11308@lazy.lzy> <20370.33554.998900.245328@tree.ty.sabi.co.UK> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20370.33554.998900.245328@tree.ty.sabi.co.UK> Sender: linux-raid-owner@vger.kernel.org To: Peter Grandi Cc: Linux RAID List-Id: linux-raid.ids Hi Peter, > Perhaps it was not clear that "use self repairing coding > similarly to Parchive" does not mean the same as "use Parchive". sorry, I understood you meant storing somewhere files with parities. > Applying self repairing coding to RAID might be easier to > imagine considering of a RAID volume as a directory of > stripe-sized files. Exactly, but as far as I know this is the same as any N parities RAID. I mean, the mathematics and algorithm behind should be exactly the same... bye, -- piergiorgio