This bug has now resurfaced in the latest development version of the kernel for jaunty! I'm now holding back and using the 2.26.27-8-generic version of the kernel that was for intrepid.
The same thing happens as what I described above, if I start the computer using any of the 2.26.28 kernels it will hose my ext3 partition that is 380gb. When I restart my computer I'm stuck with a file system check that starts cleaning up a bunch of inodes and stuff. Usually fsck is able to do it's job and put everything back in place but sometimes I have ended up losing some data. ** Summary changed: - EXT3 file system gets corrupted w/ 2.6.27 + EXT3 filesystem corrupts with 2.6.27 and 2.6.28 kernels -- EXT3 filesystem corrupts with 2.6.27 and 2.6.28 kernels https://bugs.launchpad.net/bugs/282550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
