Re: ubifs error at boot "bad node type"

[Artem Bityutskiy <dedekind1@gmail.com>]

On Wed, 2014-07-16 at 14:26 +0200, Richard Genoud wrote:
> 2014-07-16 14:02 GMT+02:00 Richard Weinberger <richard.weinberger@gmail.com>:
> > On Wed, Jul 16, 2014 at 10:29 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> >> On Tue, 2014-07-08 at 12:10 +0200, Richard Genoud wrote:
> >>> ubiattach is ok:
> >>> # ubiattach -m 3
> >>> [   50.164062] UBI: default fastmap pool size: 95
> >>> [   50.164062] UBI: default fastmap WL pool size: 25
> >>
> >> I do not know why this happened, I never saw reports like this before.
> >> Most probably this is because of fastmap. I did not hear any report that
> >> it was extensively verified WRT power cuts, and my theory is that there
> >> is a bug in fastmap which causes this, and this may be related to power
> >> cuts. I do not have proves, but suggest you to dig in this direction.
> >> E.g., setup power-cut testing.
> >
> > The logs don't show the "attached by fastmap" message. So UBI got
> > attached by scanning.
> > So, fastmap support is here but not used.
> >
> > Only the fastmap pools are used.
> 
> Well, actually, fastmap is used on this volume when I boot from NAND.
> (and I must say, It's fast !)
> Just this time, as I boot from nfsroot, or from a unclean state,
> fastmap didn't attached UBI.
> I'll check if it's still operational.

Just a head-up: check the Kconfig message for this option, it says that
even the on-flash format for it may change, although I am not quite sure
if Richard W. still means this.

-- 
Best Regards,
Artem Bityutskiy