UBIFS Index Node Corruption - Invalid Key Type
DHANAPAL, GNANACHANDRAN (G.)
gdhanapa at visteon.com
Fri May 13 02:40:30 PDT 2016
On Thu, May 12, 2016 at 03:29:56PM +0200, Richard Weinberger wrote:
> Am 11.05.2016 um 16:47 schrieb Richard Weinberger:
> > 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?
>
> Gave your issue another thought.
> It is possible that you're facing bitflips in UBIFS meta data
> which is not covered by the header CRC.
> At least this would explain the corruption pattern you're facing.
>
> Thanks,
> //richard
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.
This system is configured for 16 bit ecc strength including 10 bytes metadata in DATA0.
This NAND has 4K i/o Size and 224 OOB size.
Cheers
Gnana
More information about the linux-mtd
mailing list