On Jun 09, 2006 22:31 -0400, Jeff Garzik wrote: > Andreas Dilger wrote: > >the inode count per group > >is a fixed parameter for the whole filesystem that even online resizing > >cannot change. > > Correct. Fixed... at mke2fs time. Thus, with varying mke2fs runs, > inodes-per-group can vary, where it does not with online resize. Unless specified differently at format time, the inodes-per-group will be the same value (namely 16384) if the filesystem is larger than 512MB. So, yes, I agree with you if you start with a tiny filesystem and try to resize it to a gigantic filesystem you will get a different number of inodes, but that is true whether this is online resizing or offline. That said, for anyone who has resized their filesystem I think they prefer to be able to resize it than not being able to do so at all. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
