JFFS2 powerfail ?

[Ram]

What about the Empty Flash Messages?.

I get plenty of them.

i thought JFFS2 was having a problem with 0xFF data blocks.
whether padding the filesystem with 0xff using 'nand write' (mtd utils)
causes it?


Regards,
sriram

On 4/23/08, Artem Bityutskiy <dedekind at infradead.org> wrote:
> On Wed, 2008-04-23 at 18:48 +0100, Jamie Lokier wrote:
>  > Artem Bityutskiy wrote:
>  > > > JFFS2 notice: (791) check_node_data: wrong data CRC in data node at 0x01062120: read 0xfac2f85a, calculated 0x9ac0c6d1.
>  > > > JFFS2 notice: (791) check_node_data: wrong data CRC in data node at 0x002b9bf0: read 0x9f182fab, calculated 0x4ad20e5f.
>  > > > JFFS2 notice: (791) check_node_data: wrong data CRC in data node at 0x002b5d60: read 0x79a2a9d8, calculated 0x35234c9a.
>  > >
>  > > This is normal. It's just half-written nodes which correspond to the
>  > > last writes you made before the power cut. They are harmless, although
>  > > spam the syslog. JFFS2 cannot remove them straight after mount, so they
>  > > may accumulate. Which means each time you see corruption messages for
>  > > the previous unclean reboots. However, the corrupted nodes will go away
>  > > some time, when JFFS2 decides to garbage-collect corresponding
>  > > eraseblocks. IOW, don't worry, this is a feature.
>  >
>  > If they are going to be removed at the next GC, it would be nice to
>  > remove them earlier by overwriting them with all-1s - would that work?
>  >
>
>
> Yes, it is not a big problem to remember such blocks on scan and then
>  garbage collect them. Its just nobody cared enough to implement this.
>  You could try :-)
>
>
>  --
>  Best regards,
>  Artem Bityutskiy (Битюцкий Артём)
>
>
>  ______________________________________________________
>
> Linux MTD discussion mailing list
>  http://lists.infradead.org/mailman/listinfo/linux-mtd/
>