Re: UBIFS Index Node Corruption - Invalid Key Type

[Richard Weinberger <richard@nod.at>]

Am 11.05.2016 um 13:16 schrieb DHANAPAL, GNANACHANDRAN (G.):
>> Is this a pristine UBIFS with all fixes applied?
>> Your kernel is rather old. Not sure if we ever had such an issue,
>   Yes, This is pretty much older one provided by chip vendor NXP(Freescale) BSP 3.10.17.
>   Last commit id for ubifs is 
> 
> 	commit 4791df938fe7aa27a9fe50e4582efd583a045541
> 	Author: Richard Genoud <richard.genoud@gmail.com>
> 	Date:   Tue Apr 2 12:24:37 2013 +0200
> 
>   Last commit id for ubi is 
> 
> 	commit d779146e04aacc8abe8d645284388c837d5d50cd
> 	Author: Huang Shijie <b32955@freescale.com>
> 	Date:   Wed Sep 18 10:17:39 2013 +0800	

rw@sandpuppy:~/linux (master $)> git show d779146e04aacc8abe8d645284388c837d5d50cd
fatal: bad object d779146e04aacc8abe8d645284388c837d5d50cd

For both commits. So, a rebased tree.

:-(

>  
>> but still...
>> Can you please explain a bit more what your device is doing and what
>> NAND/UBI layout you are using?
>  This is an automotive infotainment system  that has 5 raw partitions for
>  u-boot, kernel and recovery software. And there are 3 ubifs partitions for 
> 	1.  / - (RO) -  896 MB, 
> 	2. /var - (RW) - 128 MB, 
> 	3. /meta - (RW)- 512 MB. 
> 
>  All of these partition has been through following  commands (in order) for 
>  ubifs file system creation during production.
> 	1. ubiformat
> 	2. ubimkvol
> 	3. ubiattach
> 	4. mount -t ubifs
>  A rootfs tar file from yocto build output files  was untar in / and /var partitions. 
> 
> 
>  /meta partition is configured as home folder that has runtime files for 
>  pulseaudio, gstreamer, infotainment radio tuner alignment and radio channel preset. 
>  this partition also has mount point for USB storage device. Where the user can plug 
>  and unplug their USB flash pen drive without umount -ing  it. This is the partition 
>  that got corrupted in two units out of 1000 units in vehicles  that has running for  
>  last 6 months.

What exactly is the error message you get from the kernel while mounting?
Something like "bad node type (255 but expected 9)"?
It seems like some LEBs are erased with shouldn't.

Thanks,
//richard