After some more investigation I finally noticed that all the dmesg
errors were about the same inode, so I found the files stored in it,
deleted them (luckily nothing important was there) and now the errors
are gone. Also, one of the files was Chrome's cache so it explains the
Chrome's segfault. I a
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested
the upstream kernel, please remove the 'needs-upstream-testing' tag(Only
that one
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
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 logic
--
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/+sourc
