From: Richard Weinberger <richard@sigma-star.at>
To: "Sourabh Jain (R&D - Telecom)" <sourabh.jain@matrixcomsec.com>,
"Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS node corruption issue
Date: Fri, 15 Jun 2018 09:25:39 +0200 [thread overview]
Message-ID: <11266688.7aeLSOnTp9@blindfold> (raw)
In-Reply-To: <CAAR3sxPDGVtdTkWD23GOdqB_BAp0EACOoSUeq8zAjWB5JYSsAA@mail.gmail.com>
Am Freitag, 15. Juni 2018, 09:19:46 CEST schrieb Sourabh Jain (R&D - Telecom):
> We did not enabled the xattr in the ubifs filesystem in kernel configuration.
Ok.
> Also, we had kept a setup with integck utility of mtd-utils to stress
> test ubifs. In this case, we found a separate error of "corrupt empty
> space at some index LEB". Due to this, the mtd partition was not
> mount.
> So, in which portion (UBIFS, UBI Driver, MTD drivers or NAND Driver?)
> we should work to resolve this problem?
At the MTD layer. In recent kernels we made sure that MTD drivers don't
report ECC errors to UBI when an empty page has bitflips.
See gpmi-nand.
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
next prev parent reply other threads:[~2018-06-15 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d03e8f457821494f951fabac2933bbfe@SIWEX5A.sing.micron.com>
2018-06-11 5:19 ` Re: UBIFS node corruption issue Sourabh Jain (R&D - Telecom)
2018-06-11 7:05 ` Richard Weinberger
2018-06-15 6:27 ` Richard Weinberger
2018-06-15 7:19 ` Sourabh Jain (R&D - Telecom)
2018-06-15 7:25 ` Richard Weinberger [this message]
2018-06-01 4:25 Sourabh Jain (R&D - Telecom)
2018-06-01 8:28 ` Richard Weinberger
2018-06-01 12:23 ` Sourabh Jain (R&D - Telecom)
2018-06-01 12:49 ` Richard Weinberger
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=11266688.7aeLSOnTp9@blindfold \
--to=richard@sigma-star.at \
--cc=beanhuo@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=sourabh.jain@matrixcomsec.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).