On Wed, Apr 01, 2015 at 07:35:13PM -0700, Darrick J. Wong wrote: > Most of the e2fsprogs utilities set the IO block size multiple times > (once to 1k to read the superblock, then again to set the real block > size if we find a real superblock). Unfortunately, the undo IO > manager only lets the block size be set once. For the non-mke2fs > utilities we'd rather catch the real block size and use that. mke2fs > of course wants to use a really large block size since it's probably > writing a lot of data. > > Therefore, if we haven't written any blocks to the undo file, it's > perfectly fine to allow block size changes. For mke2fs, we'll modify > the IO channel option that lets us set the huge size to lock that > in place. This greatly reduces index overhead for undo files for > e2fsck/tune2fs/resize2fs while continuing the practice of reducing > it even more for mke2fs. > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> Applied, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
