Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1390243
| From | One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: EXT4 bad block |
| Date | 2016-04-28 16:20 +0200 |
| Message-ID | <rsUXo-4ze-19@gated-at.bofh.it> (permalink) |
| References | <rsQK6-WE-13@gated-at.bofh.it> |
| Organization | Intel Corporation |
On Thu, 28 Apr 2016 09:44:16 +0000 "Lay, Kuan Loon" <kuan.loon.lay@intel.com> 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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
EXT4 bad block "Lay, Kuan Loon" <kuan.loon.lay@intel.com> - 2016-04-28 11:50 +0200
Re: EXT4 bad block One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> - 2016-04-28 16:20 +0200
Re: EXT4 bad block - ext4_xattr_block_get Philipp Hahn <pmhahn@pmhahn.de> - 2016-05-02 08:50 +0200
RE: EXT4 bad block - ext4_xattr_block_get "Lay, Kuan Loon" <kuan.loon.lay@intel.com> - 2016-05-09 04:00 +0200
csiph-web