UBIFS errors when file-system is full

[Bhuvanchandra DV]

On 07/16/2015 12:45 PM, Richard Weinberger wrote:

> Am 16.07.2015 um 09:11 schrieb Bhuvanchandra DV:
>> On 07/16/2015 12:19 PM, Richard Weinberger wrote:
>>
>>> Am 16.07.2015 um 08:09 schrieb Richard Weinberger:
>>>> Am 16.07.2015 um 07:58 schrieb Bhuvanchandra DV:
>>>>> Power cut test with 4.1.2 kernel:
>>>>>
>>>>> Preparing UBI image using mkfs.ubifs utility:
>>>>>
>>>>> $ mkfs.ubifs -c 8112 -e 124KiB -m 2KiB -o ubifs.img -r rootfs/ -v
>>>>>
>>>>>
>>>>> Flashing UBI image from U-Boot:
>>>>>
>>>>> # fatload ${interface} 0:1 ${loadaddr} ubifs.img
>>>>> reading ubifs.img
>>>>> 108691456 bytes read in 7139 ms (14.5 MiB/s)
>>>>> # ubi part ubi && ubi check rootfs || ubi create rootfs
>>>>> UBI: default fastmap pool size: 50
>>>>> UBI: default fastmap WL pool size: 25
>>>>> UBI: attaching mtd1 to ubi0
>>>>> UBI: attached by fastmap
>>>>> UBI: fastmap pool size: 50
>>>>> UBI: fastmap WL pool size: 25
>>>>> UBI: attached mtd1 (name "mtd=3", size 126 MiB) to ubi0
>>>>> UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
>>>>> UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
>>>>> UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
>>>>> UBI: good PEBs: 1003, bad PEBs: 5, corrupted PEBs: 0
>>>>> UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
>>>>> UBI: max/mean erase counter: 14/4, WL threshold: 4096, image sequence number: 0
>>>>> UBI: available PEBs: 0, total reserved PEBs: 1003, PEBs reserved for bad PEB handling: 15
>>>>> # ubi write ${loadaddr} rootfs ${filesize}
>>>>> 108691456 bytes written to volume rootfs
>>>>>
>>>>> With 4.1.2 kernel after ~600 power cut cycles, no issues with mounting the ubifs,
>>>>> but observed few stack traces.
>>>> But your kernel log shows an issue. It is not clear whether it comes from fastmap.
>>> BTW: I forgot to ask one thing, did you test using fm_debug?
>> No, if needed i can do the test again with fm_debug enabled.
>> Enabled fm_debug now with the corrupted ubifs, no addiditional debug logs observed.
> Okay. So far it does not really sound like a fastmap issue.
> But please double check using fm_debug.

Ok

>
> P.s: Why are you writing me privately?

My bad! some how in one my reply to previous mail i missed reply-all.
Will forward previous conversations to ML.

>
> Thanks,
> //richard
>
Best regards,
Bhuvan