2.6.28-11 causes massive data corruption on 64 bit installations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Manoj Iyer | ||
Bug Description
Binary package hint: linux-image-
I had on my notebook ubuntu running now for more than two years, from gutsy and going through all development releases. I was always using JFS as my root filesystem and NVIDIA binary drivers.
Notebook is a COMPAL clone from an italian assembler, SANTECH. Attached will find the lshw output.
-) I started upgrading to jaunty a week after intrepid was out. All upgrades went ok for months, until this last week switch to 2.6.28-11 kernel. Without a system crash, silently JFS started to glitch. Files started to disappear. No messages from kernel, except applications started to segfault. FIrst apt, then python, then system was lost. I repeat, when problem occurred, no kernel messages. just application segfaulting.
-) Reboting leaded to JFS repairing himself, each time loosing files (messages on tepair were something like d_ino != inode, can't exactly remember. read ahead).
-) First tought was something wrong with disk, so I just started from sysrescuecd and launched smartctl long test on disk. No problem reported, and I am still far from end of disk life.
-) Second thought was something went wrong with filesystem, and reading ext4 threads, thought developers screw up things in journaling, but I was told it was not the case.
-) As my system was in a terrible mess, lost tens of files, I installed fresh jaunty Alpha alpha6. Installation went ok. System was up again. No installation problems.
-) Went on system upgrade. Installed again 2.6.28-11. Reboot, same problems as before: applications started to segfault in series. At reboot, again filesystem problems....
-) Next try: installed this time on ext4. Again installation of fresh alpha 6 ok. And again on system upgrade same behaviour, this time leading to complete filesystem whoes (unable to mount).
-) Again I installed fresly alpha6, this time leaving 2.6.28-9. This situation seems stable.
Summary of this.
I have not too much to report, as I have no messages from kernel when problems appear, except segfaults from applications. Seems my disk I/O system gets crazy switching to 2.6.28-11. As this happens both with jfs AND ext4, seems something related to controller and/or common I/O.
Have no more hints....
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
summary: |
- jaunty kernel 2.6.28-11 kernel destroy system + jaunty kernel 2.6.28-11 kernel update renders the system un-usable. |
Changed in linux (Ubuntu): | |
assignee: | nobody → manjo |
summary: |
- jaunty kernel 2.6.28-11 kernel update renders the system un-usable. + jaunty kernel 2.6.28-11 kernel update makes the system unusable. |
Changed in linux (Ubuntu): | |
importance: | High → Critical |
tags: | added: amd64 |
summary: |
- jaunty kernel 2.6.28-11 kernel update makes the system unusable. + 2.6.28-11 causes data corruption with ICH8 on 64 bits installations |
summary: |
- 2.6.28-11 causes data corruption with ICH8 on 64 bits installations + 2.6.28-11 causes massive data corruption with ICH8/ICH9 on 64 bits + installations |
summary: |
- 2.6.28-11 causes massive data corruption with ICH8/ICH9 on 64 bits - installations + 2.6.28-11 causes massive data corruption on 64 bit installations |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
status: | In Progress → Confirmed |
tags: | added: cherry-pick |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Same issue over here. Saturday I decided to give Jaunty a try, after a collegue of mine warned for the issues with ext4.
I looked out that the dist-upgrade wouldn't touch the filesystem NOR update it. Nevertheless:
* First boot OK, few time crashing nautilus & applets in gnome though
* Reboot and everything was f*cked
* sbin/init* was gone
* fsck'd both home&root partition to recover
* yesterday night it was up and running again, so I figured I could work 'normally' today on my laptop again
* this morning I boot, login into gnome -> CRASH. Apparently some configuration issues, figured that my root filesystem was mounted read only. So again, fsck and a shitload of files in Lost+Found now
I have a Compal as well btw. A JFL92 (see attachment)
Hope you guys figure out whats going on before the official release next month.
Cheers & keep up the good work