From: Richard Weinberger <richard.weinberger@gmail.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>
Cc: Richard Weinberger <richard@nod.at>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
"zhangyi \(F\)" <yi.zhang@huawei.com>
Subject: Re: [PATCH] ubifs: Don't discard nodes in recovery when ecc err detected
Date: Sun, 1 Mar 2020 21:46:21 +0100 [thread overview]
Message-ID: <CAFLxGvyJdWcXQt3H2aknTuGhCJpV5YvAbW_wuHfs3m+KcNSjtw@mail.gmail.com> (raw)
In-Reply-To: <1582293853-136727-1-git-send-email-chengzhihao1@huawei.com>
Zhihao Cheng,
On Fri, Feb 21, 2020 at 2:57 PM Zhihao Cheng <chengzhihao1@huawei.com> 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?
> 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?
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-03-01 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 14:04 [PATCH] ubifs: Don't discard nodes in recovery when ecc err detected Zhihao Cheng
2020-03-01 20:46 ` Richard Weinberger [this message]
2020-03-02 3:58 ` Zhihao Cheng
2020-03-02 21:14 ` Richard Weinberger
2020-03-03 6:13 ` Zhihao Cheng
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=CAFLxGvyJdWcXQt3H2aknTuGhCJpV5YvAbW_wuHfs3m+KcNSjtw@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
--cc=yi.zhang@huawei.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).