Re: write error while using UBI/UBIFS

[Artem Bityutskiy <dedekind@infradead.org>]

On Mon, 2009-06-08 at 19:13 -0700, Manoj wrote:
> Thanks for the pointers. But I am using kernel v2.6.27.7. :-(

If you look at the URL I sent you, you'll find 2.6.27 back-port.
All you need to do is to apply already prepared patches to your
tree.

> 
> Meanwhile, I disabled all extra checks and
> CONFIG_MTD_NAND_VERIFY_WRITE as recommended. Now, I see this when I
> unmount and re-mount ubifs:
> 
> # mount -o sync -t ubifs ubi0:rootfs /tmp/flash/
> [  101.480000] UBIFS error (pid 164): ubifs_scan: corrupt empty space
> at LEB 1:14336
> [  101.490000] UBIFS error (pid 164): ubifs_scanned_corruption:
> corrupted data at LEB 1:14336
> [  101.500000] UBIFS error (pid 164): ubifs_scan: LEB 1 scanning failed
> [  101.530000] UBIFS error (pid 164): ubifs_recover_master_node:
> failed to recover master node
> mount: mounting ubi0:rootfs on /tmp/flash/ failed: Invalid argument

I do not see this with the newest UBI/UBIFS. Please, update yours.
See here: http://git.infradead.org/users/dedekind/ubifs-v2.6.27.git

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)