Comment 155 for bug 330824

Sorry for not checking in sooner, I've been swamped with upstream issues with ext4, and this is pretty clearly an Ubuntu specific bug. Maybe later this weekend I'll have time to try to figure out which ones of the Ubuntu-backported patches is responsible for the problem.

However, I wanted to report that I have tried to reproduce the bug using 2.6.28-11.15 with a Ubuntu Jaunty userspace, using a filesystem that was originally an image dump of an ext3 filesystem, converted to ext4 using "tune2fs -O extents,dir_index,uninit_bg /dev/mini/testext4; e2fsck -fDp /dev/mini/testext4". I then mounted it using 2.6.28-11.15, and then ran the hang.py python script attached to this bug report. The system that I used was an Lenovo S10 with an N270 Atom processor with 512 megs of memory. This is apparently all of the ideal conditions reported by those who can reproduce the problem ---- and I was not able to reproduce the problem. This makes it even more difficult for me to determine which one of the Ubuntu backports is responsible.

Random question --- people have reported that using the uptream kernels, without the Ubuntu sauce patches, have fixed the problem for them. Has anyone tried using the 2.6.30-7.8 Karmic kernel? Has anyone been able to reproduce the problem using the Karmic Koala Kernel? Or does that kernel also work w/o problems, just as the mainline 2.6.28, 2.6.29, and 2.6.30-rc6 kernels also apparently seem to be free of this bug?