UBIFS failed to recover master node
dedekind1 at gmail.com
Thu Jun 10 09:14:04 EDT 2010
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.
> 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.
Artem Bityutskiy (Артём Битюцкий)
More information about the linux-mtd