UBIFS corruption bug

[Maurizio Lombardi <m.lombardi85@gmail.com>]

    Hi all,


    I need some help with a problem with the UBIFS on a custom MPC5125-based board.

    First of all, we are running Linux 3.5.7 with a modified mpc5125_nfc driver;
    I ran the mtd tests and all of them were successful with the exception of the
    mtd_oobtest that failed.

    [...]
    mtd_oobtest: error: verify failed at 0x3da000
    mtd_oobtest: error: verify failed at 0x3db000
    mtd_oobtest: error: verify failed at 0x3dc000
    [...]

    By the way, I've read that the flash device probably does not support
    writing oob-only and that I shouldn't worry about this test.

    That said, Linux successfully boots from the ubifs-formatted NAND device and
    apparently it works flawlessly.
    The problem is that sometimes the filesystem gets corrupted and at mount the recovery
    process fails to fix it. This is the error I get at boot time:

    UBIFS: recovery needed
    UBIFS error (pid 1): ubifs_recover_leb: corruptio 0
    UBIFS error (pid 1): ubifs_scanned_corruption: corruption at LEB 404:376832
    UBIFS error (pid 1): ubifs_scanned_corruption: first 8192 bytes from LEB 404:376832
    UBIFS error (pid 1): ubifs_recover_leb: LEB 404 scanning failed
    VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -117
    Please append a correct "root=" boot option; here are the available partitions:
    1f00            2048 mtdblock0  (driver?)
    1f01         4161536 mtdblock1  (driver?)
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

    I tried to debug the ubifs to find what is going wrong, I noticed that
    the ubifs_recover_leb() function calls ubifs_scan_a_node(),
    the latter returns SCANNED_A CORRUPT_NODE and subsequently the no_more_nodes() function
    is called.

    no_more_nodes() skips the corrupt node and does a check to verify that after
    the corrupt node there is only empty space by calling is_empty(buf + skip, len - skip);
    is_empty() returns false and the recover procedure fails.


    Is there someone that could give me an advice on how to proceed to fix
    the problem?

    What could cause this problem? A bug in the mpc5125 nfc driver or a bug in ubi/ubifs ?

    Thank you in advance,
    Maurizio Lombardi