public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-mtd@lists.infradead.org,
	Koen Vandeputte <koen.vandeputte@ncentric.com>,
	Scott Bowman <wbowma01@harris.com>,
	Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: Does modern UBI/UBIFS still suffer from the 'unstable bits issue'?
Date: Sat, 03 Mar 2018 11:40:31 +0100	[thread overview]
Message-ID: <3359334.BzATs06viZ@blindfold> (raw)
In-Reply-To: <CAJ+vNU3JhZRFfh-GC+SDXe0ynQadt1Yup4vLFfGuzRy_c5a8QQ@mail.gmail.com>

Tim,

Am Freitag, 2. März 2018, 17:20:57 CET schrieb Tim Harvey:
> > Just to be sure, this is SLC NAND, right?
> 
> No, its a MT29F16G08 16GB MLC

Sorry, MLC NAND is not supported by UBI and UBIFS [0].

The ECC errors you are facing are most likely caused by paired pages.
On MLC NAND, pages come in pairs. If a write operation is interrupted, not 
only the current page is corrupted like on SLC, also the already written 
paired page is lost too.
Boris Brezillon and I spent a lot of time in addressing this problem but came 
to no good solution after all.
Well, we had a solution but it needs a lot of testing and fine tuning, sadly 
we run out of budget.
Beside of that, read and write disturb are also an important factor, this can 
be addressed with the experimental ubihealthd.

Thanks,
//richard

[0] http://linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc

  parent reply	other threads:[~2018-03-03 10:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 16:15 Does modern UBI/UBIFS still suffer from the 'unstable bits issue'? Tim Harvey
2018-03-01 16:32 ` Richard Weinberger
2018-03-02  1:19   ` Tim Harvey
2018-03-02 10:07     ` Richard Weinberger
2018-03-02 16:20       ` Tim Harvey
2018-03-02 17:33         ` Han Xu
2018-03-03 10:40         ` Richard Weinberger [this message]
2018-03-05 17:05           ` Tim Harvey

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=3359334.BzATs06viZ@blindfold \
    --to=richard@nod.at \
    --cc=adrian.hunter@intel.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=dedekind1@gmail.com \
    --cc=koen.vandeputte@ncentric.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tharvey@gateworks.com \
    --cc=wbowma01@harris.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