From owner-freebsd-stable@FreeBSD.ORG Wed Nov 24 18:34:02 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7D1D16A4CE for ; Wed, 24 Nov 2004 18:34:02 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F26243D1F for ; Wed, 24 Nov 2004 18:34:02 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1CX1uV-000JD9-Kc for stable@freebsd.org; Wed, 24 Nov 2004 19:30:35 +0100 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1CX1uS-000JCu-Cy for stable@freebsd.org; Wed, 24 Nov 2004 19:30:35 +0100 Received: from ranger.anduin.net ([81.0.162.52] helo=[192.168.1.10]) by anduin.net with esmtp (Exim 4.43 (FreeBSD)) id 1CX1uS-000JCr-5D; Wed, 24 Nov 2004 19:30:32 +0100 In-Reply-To: <20041124171115.GP7232@darkness.comp.waw.pl> References: <41A45A3F.5010008@anduin.net> <20041124171115.GP7232@darkness.comp.waw.pl> Mime-Version: 1.0 (Apple Message framework v675) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <6579E984-3E47-11D9-9576-000D9335BCEC@anduin.net> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Wed, 24 Nov 2004 19:33:55 +0100 To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.675) X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=7.5 tests=BAYES_00 autolearn=ham version=2.64 cc: stable@freebsd.org Subject: Re: graid3 - requirements or manpage wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 18:34:02 -0000 On 24. Nov 2004, at 18:11, Pawel Jakub Dawidek wrote: > On Wed, Nov 24, 2004 at 10:54:07AM +0100, Eirik ?verby wrote: > +> to the best of my ability I have been investigating the 'real'=A0 > +> requirements of a raid-3 array, and cannot see that the following=20= > text=A0 > +> from graid3(8) cannot possibly be correct - and if it is, then the=A0= > +> implementation must be wrong or incomplete (emphasis added): > +>=A0 > +> label=A0 =A0 =A0 Create a RAID3 device.=A0 The last given component = will=20 > contain > +>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 parity data, all the rest - regular = data.=A0 ***Number=20 > of=A0 > +> compo- > +>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 nents has to be equal to 3, 5, 9, = 17, etc. (2^n +=20 > 1).*** > +>=A0 > +> I might be wrong, but I cannot see how a raid-3 array should=20 > require=A0 > +> (2^n + 1) drives - I am fairly certain I have seen raid-3 arrays=A0 > +> consisting of four drives, for example. This is also what I had=20 > hoped to=A0 > +> accomplish. > > This requirement is because we want sectorsize to be power of 2 > (UFS needs it). > In RAID3 we want to send every I/O request to all components at once, > that's why we need sector size to be N*512, where N is a power of 2=20 > value > AND because graid3 uses one parity component we need N+1 providers. OK I see, makes sense. So it's not really a raid3 issue, but an=20 implementation issue. The only problem then is - gvinum being in a completely unusable state=20= (for raid5 anyway), what are my alternatives? I have four 160gb IDE=20 drives, and I want capacity+redundancy. Performance is a non-issue,=20 really. What do I do - in software? /Eirik > > > --=A0 > Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = http://www.FreeBSD.org > pjd@FreeBSD.org =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = http://garage.freebsd.pl > FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Am I = Evil? Yes, I Am! On 24. Nov 2004, at 18:11, Pawel Jakub Dawidek wrote: On Wed, Nov 24, 2004 at 10:54:07AM +0100, Eirik ?verby wrote: +> to the best of my ability I have been investigating the 'real'=A0 +> requirements of a raid-3 array, and cannot see that the following=20 text=A0 +> from graid3(8) cannot possibly be correct - and if it is, then the=A0 +> implementation must be wrong or incomplete (emphasis added): +>=A0 +> label=A0 =A0 =A0 Create a RAID3 device.=A0 The last given component = will=20 contain +>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 parity data, all the rest - regular = data.=A0 ***Number=20 of=A0 +> compo- +>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 nents has to be equal to 3, 5, 9, 17, = etc. (2^n +=20 1).*** +>=A0 +> I might be wrong, but I cannot see how a raid-3 array should require=A0= +> (2^n + 1) drives - I am fairly certain I have seen raid-3 arrays=A0 +> consisting of four drives, for example. This is also what I had=20 hoped to=A0 +> accomplish. This requirement is because we want sectorsize to be power of 2 (UFS needs it). In RAID3 we want to send every I/O request to all components at once, that's why we need sector size to be N*512, where N is a power of 2=20 value AND because graid3 uses one parity component we need N+1 providers. OK I see, makes sense. So it's not really a raid3 issue, but an=20 implementation issue. The only problem then is - gvinum being in a completely unusable state=20= (for raid5 anyway), what are my alternatives? I have four 160gb IDE=20 drives, and I want capacity+redundancy. Performance is a non-issue,=20 really. What do I do - in software? /Eirik --=A0 Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = http://www.FreeBSD.org pjd@FreeBSD.org =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = http://garage.freebsd.pl FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Am I = Evil? Yes, I Am!