UBI/UBIFS: debugging help

[Renaud Barbier]

Thanks.

I just found that after moving the files out and copying them  back
under Linux, then copying out the files works under barebox.
I will see how Linux handles the same PEBs read, maybe that will give me
a clue.




On 13/03/2015 18:42, Richard Weinberger wrote:
> On Fri, Mar 13, 2015 at 7:11 PM, Renaud Barbier <renaud.barbier at ge.com> wrote:
>> My platform is based on a ARM Cortex-A9 and boots barebox from a spi-nor.
>>
>> I have tested UBI/UBIFS from Linux on this platform with no issue after
>> disabling 4KB support for the spi nor I am using.
>>
>> However, I got problem on the boot loader side. UBI/UBIFS has been
>> ported by the barebox community from Linux and I used it successfully
>> on a previous project on a PPC platform.
>>
>> On the ARM platform I can ubiattach, mount the mtd partition and copy a
>> small file (~65KB spanning two sectors). The issue comes when I copy out
>> a larger file (512KB) out. It fails to copy the whole file.
>>
>> At the point of failure, ubifs_tnc_locate fails resulting in the
>> function read_block to return -ENOENT.
>>
>> Debugging shows that in the function ubifs_search_zbranch no keys match
>> is found prior to the failure.
>>
>> I know this list is called linux-mtd but I was hoping that somebody
>> could give me a pointer on where to look next. I am currently going
>> through git logs and mailing list.
> 
> In such situations I start with testing all layers bottom up.
> 1. Does the MTD driver work (I mean really work)
> 2. Does UBI work correctly? (ubi tests, etc...)
> 3. Same for UBIFS
> 
> HTH,
> //richard
>