Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
Jeff Garzik <[email protected]>
| Newsgroups | gmane.linux.file-systems,gmane.comp.file-systems.ext2.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
Theodore Tso wrote: > On Fri, Jun 09, 2006 at 09:43:14PM -0400, Jeff Garzik wrote: >>> ??? Can you please be specific in what the performance penalty is, and >>> what specifically is "not sized optimally" after a resize? How exactly >>> does inode allocation strategy relate to anything at all to online >>> resizing. >> Inodes per group / inode blocks per group, as I've already stated. > > Inodes per group and inode blocks per group are maintained > across an online resize. That's the problem I'm pointing out. > So there is no difference in inodes per > group for a filesystem created at size S1 and resized to size S2 > (using either an on-line or off-line resize), and a filesystem which > is created to be size S2. Trivial to prove false, by your statement above if nothing else. But anyway: Run mke2fs on a blkdev of size 500MB, and one of 500GB. Note values. Now resize blkdev formatted for size 500MB to 500GB, and note differences. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html