This bug has been open for two months, and was fixed upstream some time ago, but not in Ubuntu.
As a consequence, 2.6.28-11-generic and 2.6.28-11-server - the production release media kernels deliver silent and show-stopping data corruption, to the extent that the kernel kills user processes accessing parts of the filesystem corrupted in a particular way. That's as "game over" as it can get, and damaging for Ubuntu's image.
On the upside, there are a bunch of related fixes upstream for if the Ubuntu kernel is rebased to a newer point release, and the patch posted two months ago [1], is also probably the fixer.
This bug has been open for two months, and was fixed upstream some time ago, but not in Ubuntu.
As a consequence, 2.6.28-11-generic and 2.6.28-11-server - the production release media kernels deliver silent and show-stopping data corruption, to the extent that the kernel kills user processes accessing parts of the filesystem corrupted in a particular way. That's as "game over" as it can get, and damaging for Ubuntu's image.
On the upside, there are a bunch of related fixes upstream for if the Ubuntu kernel is rebased to a newer point release, and the patch posted two months ago [1], is also probably the fixer.
What else do we need?
[1] http:// kernel. ubuntu. com/git? p=ubuntu/ ubuntu- jaunty. git;a=commit; h=b29e79bf557ce 777878518da154f 4a0becb1de0e