"Remaining user data" on a JFFS2 image/partition

Bernhard Priewasser priewasser at gmail.com
Wed Aug 31 06:50:46 EDT 2005


Hello,

I just ran some tests on JFFS2 "space consumption" (note: total image 
size is limited due to mtdram). You can see the portion of disk space 
used for "management" information of JFFS2 depending on erase block size 
and total image size in overhead_total_size.emf (axis "Non-User-Data 
Proportion" showing percentage); the results are as expected.

overhead_scaling.emf shows absolute "overhead" space consumption in 
kilobytes depending on total image size.
-> Conclusions/Questions:

1) JFFS2 needs at least total_size = 4*erase_size to mount (wow...)

2) While total_size <= 32*erase_size JFFS2 "overhead" does NOT vary.
    Why?

3) Overhead seems to roughly depend linear on total size. (wow...)
    But: Why only rouhgly? (Varying gradients at total_size >
    32*erase_size)

4) Out of 2) and 3): On what internal structures (number, size, ...)
    does the "overhead" exactly depend? jffs2_eraseblock, ...

Regards & Thanks,
Bernhard

PS: All preliminary.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: overhead_total_size.emf
Type: application/octet-stream
Size: 23348 bytes
Desc: not available
Url : http://lists.infradead.org/pipermail/linux-mtd/attachments/20050831/814ae36d/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: overhead_scaling.emf
Type: application/octet-stream
Size: 19208 bytes
Desc: not available
Url : http://lists.infradead.org/pipermail/linux-mtd/attachments/20050831/814ae36d/attachment-0001.obj 


More information about the linux-mtd mailing list