© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Phil,
The only suggestion I can make at this point is to use a mainline kernel. This seems to be some kind of interaction between Ubuntu "Sauce" patches and the ext4 code. People have reported success with stock 2.6.28, stock 2.6.29 and a bleeding-edge 2.6.30-rcX kernels. There have been attempts to bisect the Ubuntu Sauce patches, but not much luck. The Ubuntu kernel developers that I talked to before Jaunty shipped haven't been able to reproduce the bug, and I haven't as well, which is one of the reasons why fixing it has been slow and painful.
And I'm a volunteer, and I don't have a lot of free time, so while I've finally updated a netbook to Jaunty, I haven't had time to try to track this down, as I've got lots of other items on my todo list. (And I use my own personally built 2.6.30-rcX bleeding edge kernel, and have been using ext4 in production since July of last year, and I've never seen the problem. But then again, I don't use any of the Ubuntu proprietary drivers, I don't use Apparmor, etc., so even if I were using the Ubuntu kernel there's no guarantee I would see the problem.)
Someone has graciouslly offerred to ship me a pre-set up computer that has the problem, but my main problem right now is ENOTIME. Hopefully I'll have more time by mid-May, and hopefully someone else will be able to track this down in the meantime.
P.S. Ubuntu does ship its own pre-built stock kernels w/o any "sauce" patches. So even if you aren't up to building your own kernel, you might want to try using one of those mainline kernels.