Re: [PATCH] ubifs: Don't discard nodes in recovery when ecc err detected

[Zhihao Cheng]

å 2020/3/2 4:46, Richard Weinberger åé:
> Zhihao Cheng,
>
> On Fri, Feb 21, 2020 at 2:57 PM Zhihao Cheng <chengzhihao1@xxxxxxxxxx> wrote:
> > The following process will lead TNC to find no corresponding inode node
> > (Reproduce method see Link):
> Please help me to understand what exactly is going on.
>
> >    1. Garbage collection.
> >       1) move valid inode nodes from leb A to leb B
> >          (The leb number of B has been written as GC type bud node in log)
> >       2) unmap leb A, and corresponding peb is erased
> >          (GCed inode nodes exist only on leb B)
> At this point all valid nodes are written to LEB B, right?
Yes.
> >    2. Poweroff. A node near the end of the LEB is corrupted before power
> >       on, which is uncorrectable error of ECC.
> If writing nodes to B has finished, these pages should be stable.
> How can a power-cut affect the pages where these valid nodes sit?
I mean, the uncorrectable ECC error is caused by hardware which may lead 
to corrupted nodes detected in UBIFS. I found uncorretable ECC errors on 
my NAND, in the environment of high temperature and humidity.

At present, UBIFS ignores all EBADMSG errors, so the corrupted node is 
only considered in being caused by unfinished writing. I think UBIFS 
should consider the corrupted area caused by ECC errors in process 
ubifs_recover_leb(). no_more_nodes() will skip a read-write unit. Maybe 
the corrupted area is skipped.