On Mon, Mar 2, 2009 at 8:39 PM, Theodore Tso <tytso@xxxxxxx> wrote: > On Mon, Mar 02, 2009 at 04:28:44PM +0800, Peng Tao wrote: >> This can be caused by tune2fs -O flex_bg. And clearing flex_bg on such >> partitions is harmless. > > It's actually not necessarily harmless; e2fsck could have already > assigned new bitmap and inode tables outside of the block group. If > you want to enable this, you need to actually check to make sure all > of the block/inode bitmap blocks and inode tables are within their own > block group before allowing flex_bg to be cleared. > > - Ted > Thanks for the explanation. I will send a updated patch soon. -- Cheers, Bergwolf ................ Jean-Luc Godard - "To be or not to be. That's not really a question." -- 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
