From: Artem Bityutskiy <dedekind1@gmail.com>
To: twebb <taliaferro62@gmail.com>
Cc: Lei Wen <leiwen@marvell.com>, linux-mtd@lists.infradead.org
Subject: Re: UBIFS failed to recover master node
Date: Thu, 10 Jun 2010 16:14:04 +0300 [thread overview]
Message-ID: <1276175644.5016.38.camel@localhost> (raw)
In-Reply-To: <AANLkTilHpprYBKnYrw4wTEWjYyQBFJoJZRCwEQbSUOuP@mail.gmail.com>
On Thu, 2010-06-10 at 09:08 -0400, twebb wrote:
> >
> > Yes, HW fails to correct bit errors. Why these errors are there - this
> > it the question. May be MLC-related. You need to debug this. Or send me
> > your board, I can try to take a look
> >
> > Did you enable UBI extra self checks?
> >
>
> It does appear to be an MLC-related problem - either read or write
> disturb appears to have made an "empty" page not really empty. Would
> UBI extra self checks handle this situation? I'm not familiar with
> what the extra checks do - I'll look in the code.
No.
> Since read/write disturb errors are a trait of MLC, I'm curious how
> others are dealing with this condition? ECC can't correct for it
> because it's supposed to be a blank page, implying no ECC is present.
> So if a read or write disturb occurs and the blank page is no longer
> blank - how does driver and/or UBI/UBIFS handle this? Seems that the
> remaining "good" block data would have to be moved to another LEB and
> the current block somehow marked as dirty.
ubi_leb_change() could do this.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-06-10 13:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:22 UBIFS failed to recover master node twebb
2010-05-25 5:05 ` Artem Bityutskiy
2010-05-26 16:06 ` twebb
2010-05-26 16:32 ` Artem Bityutskiy
2010-06-08 13:44 ` twebb
2010-06-08 14:17 ` Artem Bityutskiy
2010-06-08 15:00 ` twebb
2010-06-08 15:23 ` twebb
2010-06-08 15:33 ` twebb
2010-06-10 13:08 ` twebb
2010-06-10 13:14 ` Artem Bityutskiy [this message]
2010-05-25 5:06 ` Artem Bityutskiy
2010-06-28 8:21 ` re
2010-07-13 8:48 ` Artem Bityutskiy
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=1276175644.5016.38.camel@localhost \
--to=dedekind1@gmail.com \
--cc=leiwen@marvell.com \
--cc=linux-mtd@lists.infradead.org \
--cc=taliaferro62@gmail.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 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.