From: Philipp Hahn <pmhahn@pmhahn.de>
To: "Lay, Kuan Loon" <kuan.loon.lay@intel.com>,
"tytso@mit.edu" <tytso@mit.edu>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: EXT4 bad block - ext4_xattr_block_get
Date: Mon, 2 May 2016 08:42:35 +0200 [thread overview]
Message-ID: <5726F6DB.2010701@pmhahn.de> (raw)
In-Reply-To: <61AE2E6F29F7AC4182A7076FC3478CDAC217E7@PGSMSX101.gar.corp.intel.com>
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
next prev parent reply other threads:[~2016-05-02 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:44 EXT4 bad block Lay, Kuan Loon
2016-04-28 14:10 ` One Thousand Gnomes
2016-05-02 6:42 ` Philipp Hahn [this message]
2016-05-09 1:52 ` EXT4 bad block - ext4_xattr_block_get Lay, Kuan Loon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5726F6DB.2010701@pmhahn.de \
--to=pmhahn@pmhahn.de \
--cc=adilger.kernel@dilger.ca \
--cc=kuan.loon.lay@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.