ubifs issue about xattr node when replay journal

[Richard Weinberger]

On Wed, Jul 16, 2014 at 1:08 PM, Artem Bityutskiy <dedekind1 at gmail.com> wrote:
> On Sat, 2014-07-12 at 21:36 +0800, 王丁 wrote:
>> -------- kernel 3.10 log --------
>> [   64.916532] UBIFS: background thread "ubifs_bgt0_16" started, PID 92
>> [   64.926411] UBIFS: recovery needed
>> [   65.013786] UBIFS error (pid 91): ubifs_read_node: bad node type
>> (255 but expected 3)
>> [   65.021595] UBIFS error (pid 91): ubifs_read_node: bad node at LEB
>> 88:39680, LEB mapping status 1
>> [   65.030431] Not a node, first 24 bytes:
>> [   65.034073] 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
>
> There was a similar report recently (but not about xattr) and I suspect
> "fastmap". Please, check if you use it - it is new and I did not see any
> report that it was extensively tested WRT power cuts.

To be more precisely, is CONFIG_MTD_UBI_FASTMAP=y and was the image attached
by fastmap?
The kernel log would contain the message "attached by fastmap".

-- 
Thanks,
//richard