Re: UBIFS errors when file-system is full

[Richard Weinberger <richard@nod.at>]

Hi!

Am 24.07.2015 um 16:43 schrieb Bhuvanchandra DV:
> Disabled fastmap in U-Boot, still the corruption is persistent when using
> U-Boot to mount rootfs and load kernel.

Can you please describe your boot setup in detail?
Why does U-Boot _mount_ an UBIFS? Install the kernel on an UBI static volume.

If U-Boot mounts UBIFS it has to use UBI in RW mode and therefore it has to process
fastmap or _delete_ it.

>>> The same power cut tests are done by skipping the U-Boot to mount the UBIFS. Loaded
>>> the kernel via tftp and mount the rootfs with kernel. The power cut test passed.
>>> I think U-Boot might have some issues, but not very sure.
>> To my knowledge U-Boot's fastmap support is incomplete.
>> If you *really* need fastmap in U-Boot make sure that they have backported
>> all recent fastmap changes. Fastmap is still experimental and faced a lot of fixes
>> recently.
> 
> Tested with mainline U-Boot along with few downstream patches for boot config block
> support applied, the ubifs corruption is persistant.
> 
>>
>>>> Anyway, we need to sort out what is going on.
>>>> As fm_debug does not trigger it could also be a non-fastmap issue.
>>>> Did you try your test without fastmap being enabled?
>>>>
>>>> Does your target pass UBI tests too?
>>> I'm not aware of UBI tests so far the driver passed all MTD tests.
>>> Can you please provide some pointers for UBI tests. Will run the UBI tests with
>>> driver.
>> They are in the mtd-utils source.
> 
> Not yet ran the ubi-tests. Will run the tests and share the results.

Please do so. :-)

Thanks,
//richard