https://bugzilla.kernel.org/show_bug.cgi?id=200443 --- Comment #6 from Anatoly Trosinenko (anatoly.trosinenko@xxxxxxxxx) --- Please excuse me for long delay. Hmm... Still seems to be reproducible on tytso/dev (commit 362eca70). As far as I understand, it includes this fix. Steps to reproduce: 1) Compile commit 362eca70 with the attached config for x86_64 arch 2) Run mkinitrd.sh attached -- it will create self-contained initrd 3) Unpack ext4.img (it is expected to be non-crafted, freshly created ext4 image, but I attach the precise image I tested with in case it depends on mkfs version) 4) Run qemu-system-x86_64 -kernel path/to/linux.git/arch/x86/boot/bzImage -initrd ./initrd.cpio -m 512M -drive file=ext4.img,index=0,format=raw What happens: Remounting... [ 4.812614] EXT4-fs error (device sda): ext4_has_uninit_itable:3149: comm exe: Inode table for bg 0 marked as needing zeroing [ 4.814356] EXT4-fs (sda): re-mounted. Opts: (null) -- You are receiving this mail because: You are watching the assignee of the bug.
