Re: EXT4 bad block - ext4_xattr_block_get

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Am 28.04.2016 um 11:44 schrieb Lay, Kuan Loon:
> 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". 

Interesting; I posted a similar bug report on 2016-04-19 titles
 [BUG 4.1.11] EXT4-fs error: ext4_xattr_block_get:299 - Remounting
filesystem read-only

I never got a reply.

> 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?

That one happened on 4.1.11 on a virtual machine running inside
VMware-ESX after a hardware change. Last change was to disabled the
pvscsi drivers again; the system seems to be running fine since 1 week,
but the first time it took 1 month to notice the corruption, so we're
not yet sure that the problem is solved.

Philipp
--
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



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux