Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 11 Apr 2003 10:23:49 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h3BHNhFu022786 for ; Fri, 11 Apr 2003 10:23:44 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h3BHaMVe012216 for ; Fri, 11 Apr 2003 12:36:22 -0500 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (8.12.9/americas-smart-nospam1.1) with ESMTP id h3BHNXa219804230; Fri, 11 Apr 2003 12:23:33 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.8/SGI-server-1.8) with ESMTP id h3BHNXwX44127734; Fri, 11 Apr 2003 12:23:33 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h3BHNXj09045; Fri, 11 Apr 2003 12:23:33 -0500 Subject: Re: hardware RAID sunit and swidth values? From: Steve Lord To: Derek Glidden Cc: linux-xfs@oss.sgi.com In-Reply-To: <1050081295.16906.70.camel@two.nks.net> References: <1050072633.16906.1.camel@two.nks.net> <1050073584.23735.10.camel@stout.americas.sgi.com> <1050075759.16906.48.camel@two.nks.net> <20030411162601.GA14523@pc9391.physik.uni-regensburg.de> <1050081295.16906.70.camel@two.nks.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1050081812.7806.12.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.3 Date: 11 Apr 2003 12:23:33 -0500 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-archive-position: 3641 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1688 Lines: 50 On Fri, 2003-04-11 at 12:14, Derek Glidden wrote: > (in the meanwhile, I've gone and made a Linux software-RAID5 box in the > lab to play with) > > On Fri, 2003-04-11 at 12:26, Christian Guggenberger wrote: > > > > "block units" and then in "bytes." So if I have made a RAID volume with > > > 64K stripes, should I specify a su value of 128? (128*512 = 64K) > > > > > > > no, su=64k _or_ sunit=128 ! > > > > data disks in a RAID device." So I take this to mean that if I have 8 > > > disks in a RAID5, my "sw" parameter is "8"? > > > > > > > having an 8 disk RAID5, you'll need swidth=(8-1)*sunit (=896 for your example) - if I remember some > > posts about that topic correctly.( a 8 disk RAID5 has 7 "data" disks in that > > term) > > It gets even more confusing when I do: > > # mkfs -d sunit=128,swidth=384 /dev/md4 > > on software RAID5 with 4 disks and 64k stripes, and the status screen > displays: > > data = bsize=4096 blocks=84286944, > imaxpct=25 > = sunit=16 swidth=48 blks, > unwritten=0 > > > since it apparently displays the "sunit" and "swidth" values in terms of > XFS blocks, which are 4096 bytes each.... > > Thankfully, "mkfs.xfs" with no options Just Does The Right Thing on this > machine, and sets sunit and swidth correctly when it makes the > filesystem. :) (Though it might be different with hardware RAID...) All the output units are in fsblocks, on the mkfs command line it does not know what you blocksize is all the time. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com