I tried 3.5-rc5 and got the problem fairly quickly. Went back to 3.5-rc4 and noticed I was getting ext4 buffer write sda errors in syslog for that as well... so it might be that 3.5-rc4 doesn't actually work for me either, although I haven't had rc4 go into read-only mode at all yet. Since yesterday I've gone to using 3.4. Haven't had any sda errors at all in syslog anymore. I should have been paying attention to my syslog previously already instead of just waiting for the fs to go read-only.
Unfortunately, I can't be testing any more of these kernels as I'm slowly getting more and more files getting corrupted.. and this is my home office work computer so I can't allow that. Will stay on 3.4 now. Maybe someone else can test 3.5-rc1 thru 3.5-rc3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs