CRC error when mounting UBIFS

[Leo Barnes]

Hmm, ok. I would have thought the paranoid UBI checks would be able to
find driver related problems. I have however now tried creating and
mounting ubi/ubifs through nandsim on the device, so ubifs seems to be
working well.

I have tried mtd_readtest on the driver which fails when I allow
OOB-reads. Since the driver handles ECC in hardware and I dont need to
read the OOB-data for the sake of UBI/UBIFS, this should be no
problem. When removing the oob-reads from the test, it works
perfectly.

You are probably right that what fails is unaligned/short reads, since
this is exactly the functionality that I had to add to the driver.
Does any of the mtd-tests test these kinds of reads? Might be a good
addition if not.

Will perform some more debugging. Thanks for very fast replies!
//Leo


On Thu, Jun 3, 2010 at 4:25 PM, Artem Bityutskiy <dedekind1 at gmail.com> wrote:
> On Thu, 2010-06-03 at 16:02 +0200, Leo Barnes wrote:
>> Hello!
>>
>> I am trying to create and mount an UBIFS partition and get the
>> following error when trying to mount it:
>> <7>[  397.117065] UBIFS DBG (pid 438): ubifs_start_scan: scan LEB 490:0
>> <7>[  397.117218] UBIFS DBG (pid 438): ubifs_scan: look at LEB 490:0
>> (126976 bytes left)
>> <7>[  397.117401] UBIFS DBG (pid 438): ubifs_scan_a_node: hit empty space
>> <7>[  397.117614] UBIFS DBG (pid 438): ubifs_end_scan: stop scanning
>> LEB 490 at offset 0
>> <3>[  397.119598] UBIFS error (pid 438): check_lpt_crc: invalid crc in
>> LPT node: crc 0 calc 90d1
>
> Most of the time errors like this are because of problems in the driver
> level, e.g., when the driver does not handle small or unaligned length
> reads. Did you validate your MTD driver with MTD tests?
>
> --
> Best Regards,
> Artem Bityutskiy (Артём Битюцкий)
>
>