UBIFS errors when file-system is full
Richard Weinberger
richard at nod.at
Mon Jul 20 23:14:55 PDT 2015
Hi!
Am 21.07.2015 um 08:04 schrieb Bhuvanchandra DV:
> Ran the power cut tests with fm_debug enabled, no additional logs are observed.
> After few hundred power cuts U-Boot fails to mount with -22 and kernel fails
> mounting with stack trace when reading the node.
Why U-Boot? Has U-Boot fastmap enabled?
Anyway, we need to sort out what is going on.
As fm_debug does not trigger it could also be a non-fastmap issue.
Did you try your test without fastmap being enabled?
Does your target pass UBI tests too?
> Log:
[...]
> [ 2.847326] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node type (255 but expected 3)
> [ 2.866839] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node at LEB 981:70368, LEB mapping status 1
> [ 2.887961] Not a node, first 24 bytes:
> [ 2.891864] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................
Hmm, LEB1 is unmapped.
If you disable fastmap, does this target boot as expected?
Or is this a persistent corruption?
Thanks,
//richard
More information about the linux-mtd
mailing list