Cleaning JFFS2 errors

Bernd Büttner
2008-01-17T08:45:58Z

Hi,
after working some time with the JFFS2 filesystem (on a uclinux-system with a non-mmu freescale processor)
I'm getting errors on every mount like this:

jffs2_scan_inode(): CRC failed on node at 0x00c999f0: Read 0xffffffff, calculated 0x7621c0c4
Empty flash at 0x00c99a3c ends at 0x00c99c00
Empty flash at 0x0134201c ends at 0x01342200
jffs2_scan_eraseblock(): Node at 0x01d88df8 {0x1985, 0xe001, 0x0000002f) has invalid
CRC 0x1985e001 (calculated 0x392fe03e)
JFFS2 notice: (13) read_dnode: node CRC failed on dnode at 0x1341fd4:
read 0xffffffff, calculated 0xce9c70e9

The kernel is 2.6.19 from the latest uclinux distribution 20070130.

I think these errors are the result of power-loss, misbehaving new drivers and system crashes,
and I suppose they are not critical and will be corrected by jffs2 after some time.

But delivering such systems to customers doesn't look good.

Is there a possibility to force jffs2 to correct these errors at once?

I hope so.

Bernd