Nope, sorry, I rebooted after copying the dmesg. I thought that since there is [68668.595459] EXT4-fs (nvme0n1p2): Remounting filesystem read-only in what I copied, it was enough because there is where the error started. Gonna cat the entire file the next time, but I'm afraid it'll only happend if I force my CPU too much like I did (actually this is good, because the nvme took a very long time to enter in read only mody, it's a very good progress)
Meanwhile, I think that the average of read only errors inside the VMs is like 0.8/day. I always test the main machine when these errors happen and it's always fine. The only time when it gone wrong was this one that I reported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
