http://bugzilla.kernel.org/show_bug.cgi?id=12151 --- Comment #10 from Nathan Grennan <kernel-bugzilla@xxxxxxxxxxxxx> 2009-05-02 16:29:29 --- Here is my basic experience with ext4. I had two basic problems. One was where the system would just go off into a hang. The other was this issue. This issue went away when I went with a 2.6.28+ kernel. Backporting patches didn't work for me. I say this because at the time you guys were telling me there were no new patches, but I would have issue with 2.6.27 kernels, but not 2.6.28 kernels. Later cebbert said there was something nasty in 2.6.28.1 kernels, so I upgraded to 2.6.29. I have had zero issues with ext4 since upgrading to 2.6.29. I just looked through my irc logs, and found the errors that I think caused this problem. Sandeen, I have mentioned these to you before. How I think it would go would be I would get one of these errors, the system would continue, because that is the crazy default. Then a few days later, I having not noticed these errors, would reboot the system, and receive the fsck issue above. From what I remember reading this issue was fixed. Feb 16 12:03:19 proton kernel: EXT4-fs error (device md3): ext4_mb_generate_buddy: EXT4-fs: group EXT4-fs error (device md3): mb_free_blocks: double-free of inode 0's block 321550248(bit 30632 in group 9812) -- 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
