Sorry. I accidentally changed the status from Triaged, thinking I was clicking through to more details, and it won't let me change it back. Perhaps someone can revert that change.
I was intending just to add a note that this bug has been affecting several different Ubuntu systems I maintain for myself, friends and relatives, at least one is not SSD. On my own laptop the journal ends up being corrupted about once every 2 days, sometimes once a day. I switched off the "discard" mount option last week. The following is a typical diagnostic, but the details vary. 250162.298456] EXT4-fs error (device sda1): ext4_ext_remove_space:2574: inode #1077692: comm Chrome_CacheThr: bad header/extent: invalid magic - magic 87cf, entries 10138, max 3135(0), depth 51679(0) [250162.298471] Aborting journal on device sda1-8. [250162.298587] EXT4-fs (sda1): Remounting filesystem read-only [250162.298594] EXT4-fs error (device sda1) in ext4_ext_remove_space:2637: IO failure [250162.298706] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4494: Journal has aborted In my case, the system has been reliable for months before. This trouble seemed to start on 4 October, when an Ubuntu update-manager invocation remade initrd (but the kernel didn't change from /boot/vmlinuz-3.2.0-32-generic). I'm trying Linux 3.6.2-030602-generic #201210121823 SMP Fri Oct 12 22:31:22 UTC 2012 i686 i686 i386 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
