On 09/03, Theodore Ts'o wrote: > The error means that the metadata associated with one of Chromium's > cache files had gotten corrected. You say you saw this exact same > error separated in time by three months. Yes. > Between those three months, > was the file system corruption fixed by an e2fsck run? I'll admit I have a pretty bad habit of skipping fscks when they come up, but when I got that error, my system had just remounted its main filesystem readonly, and said those scary things in dmesg, and the first thing I did was reboot and let fsck do whatever it wanted, including a number of other scary things requiring me to confirm that I wanted it to go ahead a bunch of times. So, hard to say for certain, but it seems unlikely that this correction would not have been included in that. > If not, the fact that you are getting this message twice isn't > surprising. The e2fsck program *should* have been run at each reboot, > but this error may have required manual intervention to fix up. > > If you did run e2fsck, and the file system corruptions was fixed > between the two times that you saw the EXT4-fs error message, then > that is very interesting. I would discount scribbling over kernel > memory, since it would be pretty unusual that the exact same inode and > the exact same block had gotten corrupted in exactly the same way. It > could be a bug in the graphics driver, perhaps triggered by the way > Wayland is using said graphics driver. > > That also seems fairly hard to credit, so I'm going to hope you didn't > actually run e2fsck to fix the file system corruption.... Yeah, this all seems very unlikely, yet... I have lots of photos of the fsck this time, and all the questions it asked me. But I guess I should re-fsck (forced), make sure it's all happy, check my backups, and try to repeat the problem? :/ -- "Eh, wisdom's overrated. I prefer beatings and snacks." - Unity, Skin Horse http://www.ChaosReigns.com -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
