From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 74CDD7CB5 for ; Fri, 15 Jul 2016 18:07:36 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay3.corp.sgi.com (Postfix) with ESMTP id 01EA2AC002 for ; Fri, 15 Jul 2016 16:07:32 -0700 (PDT) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by cuda.sgi.com with ESMTP id rEI43ZKoz8MElZSr for ; Fri, 15 Jul 2016 16:07:28 -0700 (PDT) Date: Sat, 16 Jul 2016 09:07:25 +1000 From: Dave Chinner Subject: Re: mkfs.xfs -d su=XXX,sw=YYY and future volume resize Message-ID: <20160715230725.GV1922@dastard> References: <20160715094647.GD3608@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20160715094647.GD3608@redhat.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Marcin Sura , xfs@oss.sgi.com On Fri, Jul 15, 2016 at 11:46:47AM +0200, Carlos Maiolino wrote: > On Thu, Jul 14, 2016 at 10:19:02PM +0200, Marcin Sura wrote: > > Hi, > > When I create filesystem I can specify su and sw paramteres which match > > underlying storage device. > > So for example, If I have raid 6 volume made of 6 + 2 disks with stripe > > size of 256k I create xfs with: > > mkfs.xfs -d su=256k,sw=6 > > But what if I will extend original volume by 2 disks. sw will 8. Will > > be there a performance panelty compared to filesystem created from > > scratch with correct sw parameter? > > BR > > Marcin > > Complementing Dave's answer, you can also mount the filesystem with new > alignment configuration. > > You can use: sunit=value and swidth=value for mounting the FS with the new > settings. man xfs for more info. That doesn't change the fact that everything that already existed in the filesystem would now be misaligned and hence have performance issues on read and/or overwrite. Only newly written data will be aligned to the new stripe width. Also, keep in mind that stripw width cahnges are an alignment change you generally canot make through the mount options. Static metadata such as allocation group headers are laid out according to the physical geometry of the filesystem, and that cannot be changed. hence the mount options can only change the stripe unit/width when they don't change the alignment constraints. e.g. doubling of the stripe width will work because the alignemtn of the stripe units is still the same. However, changing from 6 disks to 8 won't work because it is a different physical alignment... Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs