https://bugzilla.kernel.org/show_bug.cgi?id=201685 Michel Roelofs (michel@xxxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michel@xxxxxxxxxxxxxxxx --- Comment #168 from Michel Roelofs (michel@xxxxxxxxxxxxxxxx) --- Hereby my experience that may be related: [ 2451.982816] EXT4-fs error (device dm-1): ext4_iget:4831: inode #6029313: comm ls: bad extra_isize 5 (inode size 256) root@ster:/# debugfs -R 'ncheck 6029313' /dev/dm-1 debugfs 1.43.4 (31-Jan-2017) Inode Pathname 6029313 //sabnzb ncheck: Inode checksum does not match inode while doing inode scan root@ster:/# echo 2 > /proc/sys/vm/drop_caches root@ster:/# debugfs -R 'ncheck 6029313' /dev/dm-1 debugfs 1.43.4 (31-Jan-2017) Inode Pathname 6029313 //sabnzb ncheck: Inode checksum does not match inode while doing inode scan root@ster:/# echo 3 > /proc/sys/vm/drop_caches root@ster:/# debugfs -R 'ncheck 6029313' /dev/dm-1 debugfs 1.43.4 (31-Jan-2017) Inode Pathname 6029313 //sabnzb Kernel v4.19.5, CPU Intel Atom D525, Debian Linux 9.6, brand new WDC WD40EFRX-68N32N0, gcc 6.3.0-18+deb9u1. Also seen with an ext4 filesystem created on Nov 21 2018. Also seen with earlier 4.19.0 kernel, and older WDC WD30EFRX-68A in same computer. Going back to v4.18.<latest> kernel solved the issues. No disk corruption shown by e2fsck. -- You are receiving this mail because: You are watching the assignee of the bug.
