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 am still not sure what triggered the error but I
think it's likely that Virtualbox caused the damage because one of my
VMs was using rawdisk vmdk (i.e. attached to a physical disk) that is
somewhat experimental feature. This would also explain the Virtualbox'es
segfaults.
Anyway, I am sorry for confusion but I got confused myself by the
apparent coincident. This bug report can now be closed and marked as
invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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
