http://bugzilla.kernel.org/show_bug.cgi?id=14354 --- Comment #14 from Theodore Tso <tytso@xxxxxxx> 2009-10-11 19:07:10 --- Holger, could you try running same test and see if you get similar results? Alexey, when you say that the dmesg was the same for both kernels, was it _identical_? Was it always the same number of orphaned inodes which were deleted, and were the inode numbers always the same? And you're sure you didn't see anything like: EXT4-fs (dm-0): error: ext4_fill_super: journal transaction 4641626 is corrupt EXT4-fs (dm-0: Mounting filesystem read-only In Holger's report, he mentions that after the first reboot, the file system turns read-only. Holger, what do you see in your system logs after each reboot, in particular before the filesystem gets mounted or remounted read-only? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
