Re: UBIFS errors when file-system is full

[Richard Weinberger <richard@nod.at>]

Am 31.07.2015 um 18:47 schrieb Bhuvanchandra DV:
> On 07/24/2015 06:51 PM, Richard Weinberger wrote:
> 
>> 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.
> 
> U-Boot mounts UBIFS for loading the kernel and device tree blobs availabel in rootfs.
> Since approximately around ~3-5 % of spare blocks are reserverd for wear leveling
> (according to the NAND manufacturer). Initially we had a separate UBI partition of 8MB
> for Kenrel, but after few times of re-writing the kernel to that volume kernel fails
> with no available free space. Due to that reason we made a single big ubi volume and
> moved the kernel and device tree blobs to rootfs.

UBI partition? You mean UBI volume?
Just install kernel, initrd and dtb on UBI static volumes.

If U-Boot has to mount UBIFS it has to do that in RW mode.
So, no fastmap for you.

> Seems the mtd-utils are not really cross-compile friendly, some how managed to build the ubi-tests
> tweeking the Makefiles.

Seeing forward to receive patches or at least a bug report.

> The tests ran on ubi partition after isolating it from U-Boot completly.
> Formatted the ubi partition and then boot with SD card (4.1.2 kernel fastmap enabled/disabled, fm_debug enabled).
> Please find the below log of ubi-tests:
> 

> [io_paral] write_thread():222: written and read data are different

*blink*

Thanks,
//richard