On 7/31/2012 8:56 AM, Stefan Priebe - Profihost AG wrote: > 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. If you already know they *will* need 250GB, make them 250GB now. This is common sense. > Should i take care of that and format these disks with special parameters? Take care of what? Preemptively avoid what? > 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. 4 AGs is the default when an XFS is created unless the device is over 4TB. When you grow XFS, new AGs must be created in the new space. This is because once an AG is "laid down" it doesn't move and its size never changes. Any time you grow and XFS you get more AGs. This is by design. > Is it a problem if this grow will happen in small portions (30GB => 50GB > => 75GB => 100GB => ... 300GB)? It 'could' be a problem. But there's no way for us to know that without, drum roll please, you guessed it-- knowing your workload and the characteristics of the underlying storage. Wild ass guess? These are virtual machines with relatively tiny storage. Performance isn't critical or you'd not attempt this in the first place. So, I'd guess no, it won't be a problem. If on the other hand you need high performance to these filesystems, then you need to provide details of the storage device and the workloads and we'll discuss it further. -- Stan _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
