I was also a victim of this bug, in which I experienced the following: 1. My applications started receiving segfaults. I tried to strace them and found that the segfaults were mostly due to problems with files (corrupted files) 2. Then my administrative applications started segfaulting and after that my kernel wouldn't boot as a results in a heavily corrupted file system. I ran fsck.ext3 on my boot partition and all the files were corrupted.
To solve: Reinstalled ubuntu from the live CD and updated the kernel to the 2.6.29-020629. So far I have had no problem. I am a little surprised that my brother who has a 32 bit system does not have this problem with the 2.6.28-11 kernel and as it seams that only 64bit systems are affected. Can anyone with 32 bit system confirm this. I also believe that it has to do with how files are written/updated as many of the errors that fsck reported were: 1. Inode referenced in future data 2. Inode reference count too high 3. Unattached Inodes Another note is that none of my boot files (as my grub is on its own partition) were corrupted. System specs: 64 bit, Intel Core 2 duo, 4 GB ram, 320 GB WD hdd (2.5" inch) Multiboot Setup -- jaunty kernel 2.6.28-11 kernel update renders the system un-usable. https://bugs.launchpad.net/bugs/346691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
