Hi, I stumbled upon a problem with JFFS2.
When overwriting a relatively large file (580 kB in a 896 kB flash region), the file system breaks. Plenty of errors like these ensue when trying to read the new, overwritten file after a reboot: BUG() at ~/ecos-2.0.40/packages/fs/jffs2/v2_0_40/src/readinode.c 381 <5>JFFS2 notice: read_unknown: node header CRC failed at %#08x. But it must hav e been OK earlier. <4>Node totlen on flash (0xffffffff) != totlen from node ref (0x00000044) <4>JFFS2 warning: jffs2_do_read_inode_internal: no data nodes found for ino #3 <5>JFFS2 notice: jffs2_do_read_inode_internal: but it has children so we fake s ome modes for it <4>JFFS2 warning: jffs2_do_read_inode_internal: no data nodes found for ino #3 <5>JFFS2 notice: jffs2_do_read_inode_internal: but it has children so we fake s ome modes for it It does not matter if the new file is identical with the old file. Unlinking and then writing the file again causes the same result. If this is more or less a known problem, how likely is it that small files (say, being smaller than 50% of the file system's storage space) cause this behaviour as well? I noticed that the current version in the eCos source tree lags a bit behind the code in the Linux kernel. Maybe this issue has been fixed there already and only requires a port of the current code to eCos. I'd be grateful for any ideas about this problem, even if it is just pointing me to the linux-mtd mailing list. Thanks, Gunnar Ruthenberg. -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss