QUOTE(iamasmith @ Jul 31 2006, 02:37 AM)
I think this should probably be on the wiki of frequently asked questions.
There is probably more detail in one of the several responses that I have already made to this 'non issue' so I will be brief here.
jffs2 avoids writing updates until it is absolutely necessary. This is even across reboots.
The actual jffs driver is very chatty and shows the state inconsistency that occurs on the actual file system without taking into account what is pending in the journal. The actual access to the file system, however, does take into account the information stored in the journal and will provide you with a consistent file system.
The percieved errors are almost certainly non existant, you will see inode errors and errors about files no longer existing during the boot phase, this is quite normal for a jffs2 file system that has had any form of file alteration - these should be ignored unless you are actuall experiencing inconsistencies. The advice then is to reinstall and restore.
Why does jffs2 do this? - it does it because NAND flash has a limited number of write cycles and it does absolutely everything it can to limit the number of writes to the same block. This behaviour is by design.
Do you mean if I see the error again and again and never goes away (That's what I have on my C1000), then I should do a full restore? Do I have a way to "FORCE" JFFS2 to do an actual write to see if there is a real error? After all, restrong an NAND backup will end up with writing the WHOLE flash memory.
Also, by "wiki" do you mean the pdaXrom website or the one on oesf?