UBIFS Corrupt during power failure

Eric Holmberg Eric_Holmberg at Trimble.com
Tue Mar 24 13:04:02 EDT 2009


Hi Adrian,

> Please enable UBIFS debugging and set the UBIFS Default message level
to 3.

Thanks for the response.  Enabling UBIFS debugging and setting to level
3 only provides slightly more information.  

[42949375.480000] UBIFS: recovery needed
[42949376.450000] UBIFS error (pid 1): ubifs_scan: corrupt empty space
at LEB 4:44512
[42949376.460000] UBIFS error (pid 1): ubifs_scanned_corruption:
corrupted data at LEB 4:44512
[42949376.470000] UBIFS error (pid 1): ubifs_scanned_corruption: first
4096 bytes from LEB 4:44512
[42949376.490000] UBIFS error (pid 1): ubifs_scan: LEB 4 scanning failed
[42949376.540000] UBIFS error (pid 1): ubifs_recover_leb: corrupt empty
space at LEB 4:480
[42949376.550000] UBIFS error (pid 1): ubifs_scanned_corruption:
corrupted data at LEB 4:480
[42949376.560000] UBIFS error (pid 1): ubifs_scanned_corruption: first
4096 bytes from LEB 4:480
[42949376.580000] UBIFS error (pid 1): ubifs_recover_leb: LEB 4 scanning
failed
[42949376.600000] VFS: Cannot open root device "ubi0:rootfs" or
unknown-block(0,0)


> Also, could you tell us what MTD drivers you are using?
I'm using the physmap CFI flash driver for a CFI-compliant S29GL256P90F
256Mbit NOR flash chip.  Is that what you're asking for?

I'll keep working on a better way to reproduce the problem.  Let me know
if I need to add some printk statements somewhere and/or enable UBI or
MTD debugging.

Thanks,

Eric



More information about the linux-mtd mailing list