From: Richard Weinberger <richard@nod.at>
To: "DHANAPAL, GNANACHANDRAN (G.)" <gdhanapa@visteon.com>
Cc: "CN, Aananth (A.A.)" <caananth@visteon.com>,
"Gunasundar, Balamanikandan (B.)" <bgunasun@visteon.com>,
"Babu, Viswanathan (V.)" <vbabu3@visteon.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"gnanachandran@gmail.com" <gnanachandran@gmail.com>
Subject: Re: UBIFS Index Node Corruption - Invalid Key Type
Date: Fri, 13 May 2016 15:54:10 +0200 [thread overview]
Message-ID: <5735DC82.2010309@nod.at> (raw)
In-Reply-To: <20160513095004.GA6195@visteon-gnana>
Am 13.05.2016 um 11:40 schrieb DHANAPAL, GNANACHANDRAN (G.):
> Richard,
>
> I believe CRC value for a node is calculated in RAM before writing the node in NAND.
> In this case, node CRC and calculated CRC are matching. so Will there be possibility
> for corrupting key type area (32 bits) and keeping others intacted. or any other
> possibility for node getting corrupted.
I have to correct myself, the branches of an index node are covered by
the node header CRC.
This makes the whole picture more strange.
You said you're facing the same issue on another unit.
Is the corruption really the same? Bad key type 5?
Thanks,
//richard
next prev parent reply other threads:[~2016-05-13 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 12:14 UBIFS Index Node Corruption - Invalid Key Type DHANAPAL, GNANACHANDRAN (G.)
2016-05-10 13:58 ` Richard Weinberger
2016-05-10 14:49 ` DHANAPAL, GNANACHANDRAN (G.)
2016-05-10 16:23 ` Richard Weinberger
2016-05-10 16:48 ` Richard Weinberger
[not found] ` <20160511065223.GA22220@visteon-gnana>
2016-05-11 7:29 ` DHANAPAL, GNANACHANDRAN (G.)
2016-05-11 9:22 ` Richard Weinberger
2016-05-11 11:16 ` DHANAPAL, GNANACHANDRAN (G.)
2016-05-11 12:42 ` Richard Weinberger
2016-05-11 14:47 ` Richard Weinberger
2016-05-12 13:29 ` Richard Weinberger
2016-05-13 9:40 ` DHANAPAL, GNANACHANDRAN (G.)
2016-05-13 13:54 ` Richard Weinberger [this message]
2016-05-13 16:02 ` DHANAPAL, GNANACHANDRAN (G.)
2016-05-13 16:03 ` CN, Aananth (A.A.)
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=5735DC82.2010309@nod.at \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=bgunasun@visteon.com \
--cc=caananth@visteon.com \
--cc=dedekind1@gmail.com \
--cc=gdhanapa@visteon.com \
--cc=gnanachandran@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vbabu3@visteon.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).