Ted, Concerning flex_bg and uninit_bg : it's currently not possible to resize a filesystem with those features. It seems there are issues with resize2fs. We have also used nomballoc switch when mounting because of the oops when unmounting. We have tried both physical hard disk drive and loop back devices. We have tested several filesystem resize with few (adding 1 group) to many (adding 250 groups) more groups. All give correct group descriptors using dump2fs and no problem when writing files and unmounting filesystems. This is a typical test case: mkfs.ext4 -E test_fs -O ^flex_bg /dev/sdc1 10M mount -t ext4dev -o nomballoc /dev/sdc1 /mnt/test dumpe2fs /dev/sdc1 resize2fs /dev/sdc1 100M dumpe2fs /dev/sdc1 dd if=/dev/urandom of=/mnt/test/data bs=95M count=1 umount /mnt/test fsck.ext4 -f /dev/sdc1 This test being run for several sizes of filesystem (from 10M with 1K blocks to 1G with 4K blocks). Let me know if we have missed something or if you want more testings. Regards Le jeudi 12 juin 2008 à 15:04 -0400, Theodore Tso a écrit : > On Thu, Jun 12, 2008 at 11:42:34AM +0200, Frédéric Bohé wrote: > > From: Frederic Bohe <frederic.bohe@xxxxxxxx> > > Frederic, > > Many thanks! How much testing have you done with the patch? Does it > fix growing the filesystems from a filesystem with say, 18 block > groups to 32 block groups? Have you tried with with different > filesystem features, including with and without flex_bg and uninit_bg? > > Regards, > > - 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
