On Mon, Jul 31, 2017 at 7:08 PM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > On Thu, Jul 27, 2017 at 10:54 PM, Tahsin Erdogan <tahsin@xxxxxxxxxx> wrote: >> Still no luck reproducing the error. I am using the test script below >> at v4.13-rc2. Do you mind checking my script to see what I am missing? > > Don't know. I can reliably reproduce it under UML, but not with a > VM. What the hell is going on? > Is it the same ext4 image for UML and VM? same image size? same mkfs version? What inode size do you have in UML setup? e.g.: dumpe2fs -h /dev/sda3|grep Inode.size dumpe2fs 1.42.13 (17-May-2015) Inode size: 256 have extra_isize feature? (not sure if that matters) dumpe2fs -h /dev/sda3|grep isize dumpe2fs 1.42.13 (17-May-2015) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Required extra isize: 28 Desired extra isize: 28 -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
