Hi guys, I'm working on a Fedora bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=852833) together with Eric and we found that the problem described on the bugzilla happens when the commit 93f9052643 is not applied, which is the case of the Fedora 16 kernel being discussed there. Although we already found the solution to the problem in the commit above, looking through the commit have raised some questions regarding to the bitmap of the newer block groups added to the FS after it is extended. The newer block groups do not have flags ITABLE_ZEROED and INODE_UNINIT set, even when 'lazy_itable_init' is enabled. Without this commit, inode stale data might be exposed and also makes fsck complain about all inodes of the newer block groups. The question is, are these flags expected to not be found on these newer block groups or they should be set? The lack of these flags on newer block groups is an expected behaviour or is something that should be fixed? FWIW, in the old ext4_group_add(), we added EXT4_BG_INODE_ZEROED flag to the bg_flags, also, I did some tests here and the lack of these flags look to not be affecting filesystem integrity, i.e. new inodes can be properly allocated, which sounds that these uninitialized inodes/bitmaps are set to be initialized as soon as a first inode is allocated on these new BGs. Anything else I'm missing Eric? Cheers, -- Carlos -- 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
