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>,
"babu3@visteon.com" <babu3@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: Wed, 11 May 2016 16:47:16 +0200 [thread overview]
Message-ID: <573345F4.9070203@nod.at> (raw)
In-Reply-To: <20160511112630.GB22640@visteon-gnana>
Am 11.05.2016 um 13:16 schrieb DHANAPAL, GNANACHANDRAN (G.):
> On Wed, May 11, 2016 at 11:22:15AM +0200, Richard Weinberger wrote:
>> I had a brief look, the provided dump has more problems.
>> The dent node with the bad type is not referenced by the journal,
>> so we can ignore it for now.
>> The worse problem is that the index references a lot of non-existing
>> inodes.
BTW: Do both MTD tests and UBI tests pass?
Thanks,
//richard
next prev parent reply other threads:[~2016-05-11 14:47 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 [this message]
2016-05-12 13:29 ` Richard Weinberger
2016-05-13 9:40 ` DHANAPAL, GNANACHANDRAN (G.)
2016-05-13 13:54 ` Richard Weinberger
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=573345F4.9070203@nod.at \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=babu3@visteon.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 \
/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).