On Thu, 28 Apr 2016 09:44:16 +0000 "Lay, Kuan Loon" <kuan.loon.lay@xxxxxxxxx> wrote: > Hi, > > I encounter random bad block on different file, the message looks like "EXT4-fs error (device mmcblk0p14): ext4_xattr_block_get:298: inode #77: comm (syslogd): bad block 7288". > > I am using mke2fs 1.43-WIP (18-May-2015) and I saw this message "Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features." print out. > > My current kernel version is 3.14.55, what patch I need to backport to solve the bad block issue? I think you could start by providing a lot more information about the platform you see it on, the other messages logged, whether you've run memtest86 on the machine, whether it is stable if you boot a 4.4 kernel and so on. Without that information I doubt anyone can help you with your bug. Alan -- 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
