https://bugzilla.kernel.org/show_bug.cgi?id=201685 Theodore Tso (tytso@xxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tytso@xxxxxxx --- Comment #2 from Theodore Tso (tytso@xxxxxxx) --- I'm using a 4.19.0 based kernel (with some ext4 patches for the 4.20 mainline) and I'm not noticing any file system problems. I'm running a Dell XPS 13 with an NVME SSD, and Debian testing as my userspace. It's hard to do anything with a "my file system is corrupted" report without any kind of reliable reproduction information. Remember that file system corruptions can be caused by any number of things --- buggy device drivers, buggy Nvidia binary modules that dereference wild pointers and randomly corrupt kernel memory, RAID code if you are using RAID, etc., etc. Also, the symptoms reported by Claude and Jason are very different. Claude has reported that a data block in a shared library file has gotten corrupted. Jason has reported that file system metadata corruption. This could very well be coming from different root causes. So it's better with these sorts of things to file separate bugs, and to include detailed hardware configuration details, kernel configuration, dumpe2fs outputs of the file system in question, as well as e2fsck logs. -- You are receiving this mail because: You are watching the assignee of the bug.
