From: Richard Weinberger <richard@nod.at>
To: "Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: master node can not be recovered
Date: Wed, 4 Nov 2015 09:03:42 +0100 [thread overview]
Message-ID: <5639BBDE.5000604@nod.at> (raw)
In-Reply-To: <A765B125120D1346A63912DDE6D8B6310BF4FE9E@NTXXIAMBX02.xacn.micron.com>
Am 04.11.2015 um 08:43 schrieb Bean Huo 霍斌斌 (beanhuo):
>
>> On Mon, 2015-11-02 at 17:46 +0100, Richard Weinberger wrote:
>>> ubifs_recover_master_node() is very strict.
>>
>> Just like the rest of the recovery code, the master node part is consistent with
>> that.
>>
>>> Can it be that in your case more than the last written page is
>>> corrupted?
>>
>> I suspect so too.
>
> Hi, Artem
> The second master node not be corrupted. I will test again later, and send it out.
UBIFS uses two LEBs to store master nodes.
If UBIFS was interrupted (unclean reboot) while writing a master node it will double check
whether only this last written page is corrupted and then copy the node from the
second LEB.
But if two or more pages are corrupted UBIFS will give up as this most not happen
from UBIFS's point of view.
Thanks,
//richard
next prev parent reply other threads:[~2015-11-04 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 16:10 master node can not be recovered Bean Huo 霍斌斌 (beanhuo)
2015-11-02 16:46 ` Richard Weinberger
2015-11-03 9:12 ` Artem Bityutskiy
2015-11-04 7:43 ` Bean Huo 霍斌斌 (beanhuo)
2015-11-04 8:03 ` Richard Weinberger [this message]
2015-11-04 8:20 ` Artem Bityutskiy
2015-11-04 8:25 ` Bityutskiy, Artem
2015-11-04 8:40 ` Boris Brezillon
2015-11-04 8:57 ` Artem Bityutskiy
2015-12-04 7:51 ` Bean Huo 霍斌斌 (beanhuo)
2015-11-03 8:32 ` 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=5639BBDE.5000604@nod.at \
--to=richard@nod.at \
--cc=beanhuo@micron.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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).