UBIFS errors are randomly seen after reboots

[Richard Weinberger]

Chaitanya,

Am 16.01.2017 um 16:21 schrieb chaitanya vinnakota:
> Hi Richard,
> 
> Thanks for your response.
> 
> Based on your response I enabled chk_io , chk_gen,
> tst_emulate_bitflips and tst_emulate_power_failure  options in
> /sys/kernel/debug/ubi/ubi0 directory. I carried on with my test which
> keeps on creating/writing data to files in all the available nand
> partitions and during which a reboot is issued .
> 
>  Below are the various UBI messages I'm seeing quite consistently at
> different times after enabling the debug options.
> 
> 1. UBI error: do_sync_erase: cannot erase PEB 200 (emulated)
> 2. UBI error: erase_worker: failed to erase PEB 200, error -5
> 3. UBI: mark PEB 200 as bad
> 4. UBI error: ubi_io_write: cannot write 2048 bytes to PEB 452:0 (emulated)
> 5. UBI error: erase_worker: failed to erase PEB 452, error -5
>      UBI: mark PEB 452 as bad
>      Bad block table written to 0x00000ffe0000, version 0x0B
>      Bad block table written to 0x00000ffc0000, version 0x0B
>      UBI: 40 PEBs left in the reserve
> 
> Are all the above errors forecasting any doom or are they expected ?

You've enabled UBI self-tests and error *emulation*. This is not what I meant.

I had in mind:
1. MTD tests, these are available in the kernel source:
   http://linux-mtd.infradead.org/doc/general.html#L_mtd_tests
   And now also as part of mtd-utils.
2. UBI tests, you can find them in the tests/ubi-tests/ directory
   of the mtd-utils source package.

David, I think we should add a page to mtd-www on testing. :-)

Thanks,
//richard