On Sat, Jul 26, 2014 at 08:45:57AM -0400, Theodore Ts'o wrote: > Filesystem features: has_journal ext_attr resize_inode dir_index filetype > extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink > extra_isize > Block count: 5804916736 > Reserved GDT blocks: 585 > > If the block count is greater than 2**32 (4294967296), resize_inode > must not be set, and reserved GDT blocks should be zero. So this is > definitely not right. I've just tried to reproduce this on 24T->48T raid0 array (resizing from 24T to 48T), without any success. And that's why: I don't have resize_inode in filesystem features. Thanks for pointing on this, Ted. Cheers, Azat. -- 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
