mkfs.jffs2 propsal and a question about burst reads

Jörn Engel joern at
Tue Nov 6 07:13:16 EST 2001


> 1)
>    Before I can install a new JFFS2 FS image(produced with mkfs.jffs2) I have
>    to erase the whole flash partition, then copy the image(with cp image /dev/mtdlock4)
>    the device. Then I boot linux and now JFFS2 will re-erase all unused blocks. 
>    If I skip the initial erase, then JFFS2 will be confused by the earlier
>    JFFS2 contens which remain after the previous JFFS2 FS that were on the flash.
>    I think this is the expected behavior, correct?
>    I find it unconvinient and time consuming to erase the WHOLE flash partiton
>    before I can install a new FS image. Therefore I wonder if it would
>    be possible to add some flag/end marker in JFFS2 that mkfs.jffs2 could
>    set, so that JFFS2 knows that the flash space after the maker does not
>    contain valid JFFS2 data. Once JFFS2 has recongnized its FS, JFFS2 would
>    delete the end marker and resume normal behaviour. 

That would be simple, if jffs2 was strictly log-structured. But from
what I have heard/read about it, the wear levelling makes all delete
blocks equal. There is no last block, that you can mark in some way.

Hmm. BTW, is it just me, or do other peaople agree, that the j in jffs
is a bug? Journaling has little to do with a log-structure.


When your language is nowhere near Turing-complete, 
syntactic sugar can be your friend.

More information about the linux-mtd mailing list