(NAND) JFFS2 mount time

Ferenc Havasi havasi at inf.u-szeged.hu
Fri Jun 18 10:48:04 EDT 2004

David Woodhouse wrote:

>I wasn't going to do it on umount. I was going to do it at the end of
>each eraseblock. When we've almost filled an eraseblock we write a
>summary to the end of it, containing all the information which we would
>otherwise have to read from it during mount.
>That's basically a list of the { inode#, physical_offset, length } for
>each node in the eraseblock, and something about nlink. Note that
>there's a lot of redundancy in the offsets and lengths so we can
>contrive a storage method which is fairly efficient. 
>Then at mount we look first at the _end_ of each eraseblock for such a
>summary. If it exists, we read in the state from it. If not, we scan
>that particular eraseblock the old way.
Artem and our idea are very similar.

But I think your one is better. It's a little bit slower in mount time 
but much easier to implement (and also much more clean).

I think we'll start to implement it.


More information about the linux-mtd mailing list