UBIFS errors when file-system is full

[Bhuvanchandra DV]

Hi Richard,

On 08/01/2015 08:36 AM, Richard Weinberger wrote:

> 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?

Sorry, 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.

Okay

>> 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.

Sure will do it.

>
>> 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*

Tried to run the io_paral test multiple times seperately with few debug prints added to see what exact
differences with read and write buffers, so far we could see one complete page is read twice even though
it is written once. I'm now confused is the issue happen while reading or while writing. Can you give us
some pointers so that we can narrow down the cause for this failure.

>
> Thanks,
> //richard

Best regards,
Bhuvan