From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q6VDv14B184246 for ; Tue, 31 Jul 2012 08:57:02 -0500 Received: from mail.profihost.ag (mail.profihost.ag [85.158.179.208]) by cuda.sgi.com with ESMTP id zmS7P6opRPEjA2Kv (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 31 Jul 2012 06:56:59 -0700 (PDT) Message-ID: <5017E426.2040709@profihost.ag> Date: Tue, 31 Jul 2012 15:56:54 +0200 From: Stefan Priebe - Profihost AG MIME-Version: 1.0 Subject: xfs_growfs / planned resize / performance impact List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: "xfs@oss.sgi.com" Hello list, i'm planning to create a couple of VMs with just 30GB of space while using xfs as the main filesystem. Now i alreay know that some of the VMs will grow up to 250GB while resizing the block device and using xfs_growfs. Should i take care of that and format these disks with special parameters? I've discovered that a 500GB volume has agcount=4 and 64000 blocks of internal log - while a 300GB volume resized to 500GB has agcount 7 ad only 40960 blocks of internal log. Is it a problem if this grow will happen in small portions (30GB => 50GB => 75GB => 100GB => ... 300GB)? Thanks! Greets, Stefan _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs