@Olli, If the filesystem has gone read-only, then it means that the kernel has detected filesystem corruption of some kind. Use dmesg to try to get the kernel logs, or can go through /var/log/messages for older kernel messages from previous boot sessions. Feel free to file a separate bug report for such bugs (this bug is getting pretty long, and what you are describing is a distinctly separate bug report).
I will warn you that there are a very large number of filesystem corruption bugs which we have fixed since 2.6.26, and in fact at this point we are only doing backports to 2.6.27 (and there are patches queued up for 2.6.27 that are waiting for Greg K-H to do another stable kernel series release). If you are willing to compile a vanilla 2.6.29-rc7 kernel, you will probably have the best luck (and the best performance). Which, by the way, is another reason for not using proprietary binary-only kernel modules; they very often aren't available for the latest bleeding-edge kernel. I understand that some people are hesitant putting pre-release kernels on stable systems --- but quite frankly, back in the 2.6.26 and 2.6.27 days we were warning people that ext4 was still being stablized, and to think twice before putting it on production systems. Even for people putting in on their laptops, there was always a "we who are about to die salute you" attitude; early testing is critical, since that's how we get our bug reports so we can fix bugs, and people who tested early ext4 versions did us and the Linux community a huge service by reporting bugs that I wasn't seeing given my usage patterns. (For example, one bug was much more likely to show up if you were using Bittorrent, and I'm not a big bittorrent user.) Of course, once the bugs are fixed it's important to get folks moved up to newer kernels, which can sometimes be hard for them. I really wish Ubuntu had a "kernel of the week" or which provided the latest development kernel pre-packaged up, much like Fedora has. It would make it a lot easier to recommend that people try a newer kernel package. -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in “ecryptfs-utils” source package in Ubuntu: Invalid Status in “linux” source package in Ubuntu: Confirmed Status in ecryptfs-utils in Ubuntu Jaunty: Invalid Status in linux in Ubuntu Jaunty: Confirmed Bug description: I recently installed Kubuntu Jaunty on a new drive, using Ext4 for all my data. The first time i had this problem was a few days ago when after a power loss ktimetracker's config file was replaced by a 0 byte version . No idea if anything else was affected.. I just noticed ktimetracker right away. Today, I was experimenting with some BIOS settings that made the system crash right after loading the desktop. After a clean reboot pretty much any file written to by any application (during the previous boot) was 0 bytes. For example Plasma and some of the KDE core config files were reset. Also some of my MySQL databases were killed... My EXT4 partitions all use the default settings with no performance tweaks. Barriers on, extents on, ordered data mode.. I used Ext3 for 2 years and I never had any problems after power losses or system crashes. Jaunty has all the recent updates except for the kernel that i don't upgrade because of bug #315006 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: linux-image-2.6.28-4-generic 2.6.28-4.6 ProcCmdLine: root=UUID=81942248-db70-46ef-97df-836006aad399 ro rootfstype=ext4 vga=791 all_generic_ide elevator=anticipatory ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-4.6-generic SourcePackage: linux _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
