Switching to CFQ didn't help, I still see same errors in dmesg:

[ 1253.737180] EXT4-fs error (device sda3): ext4_ext_search_left:1224: inode 
#52632: comm flush-8:0: ix (5298) != EXT_FIRST_INDEX (0) (depth 0)!
[ 1253.737188] EXT4-fs (sda3): delayed block allocation failed for inode 52632 
at logical offset 5344 with max blocks 2 with error -5
[ 1253.737191] EXT4-fs (sda3): This should not happen!! Data will be lost
[ 1253.737192] 
[ 1421.134271] show_signal_msg: 81 callbacks suppressed
[ 1421.134275] chrome[3343]: segfault at bbadbeef ip 00007fb2c03c3c61 sp 
00007fff786944a0 error 6 in chrome[7fb2bea3a000+4094000]
[ 1421.222617] chrome[3489]: segfault at bbadbeef ip 00007fb2c03c3c61 sp 
00007fff78693d40 error 6 in chrome[7fb2bea3a000+4094000]


BTW. People using other distributions seem to be suffering from same bug:
https://bbs.archlinux.org/viewtopic.php?id=138532
https://bbs.archlinux.org/viewtopic.php?id=138793

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982490

Title:
  EXT4 filesystem errors after switching to SSD drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/982490/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to