jffs2-filesystem

Arno Steffen arno.steffen at googlemail.com
Fri Feb 4 07:21:15 EST 2011


I do have a question to jffs2 (using NAND flash).
My filesystem is almost empty, only a few bytes are in (see below)

...
0000120 0016 0000 0000 0000 4bed 98b5 e4ac 7bbe
0000130 6956 6f73 2072 3156 2030 202d 6f79 7275
0000140 6e20 6d61 0a65 ffff

Flashing this file to an emtpy flash (all is 0xff)I see this also in flash

If I do some fileoperation (touch a; touch b; touch c) the flash
changes to something like that (schematic):

0000130 6956 6f73 2072 3156 2030 202d 6f79 7275
0000140 6e20 6d61 0a65 ffff  ffff ffff  ....

0000800 6956 6f73 2072 0000 0000....

0001000 6e20 6d61 0a65 0000 0000 ....

0001800 6956 6f73 2072 0000 0000 ...

So it will write (multiples of )0x800 bytes and pad the not used bytes
with "00".
This is different to the original flashed file, which is padded with 0xff.
But finally this gives me a message: "empty flash at 0x148 .... 0x800".

--------

It seems that flashing of filesystem goes wrong as it is not padded to
a boundary of 0x800 with 0x00.
But I couldn't found any option in mkjffs2 to generate such files ..
Can you solve that riddle?

Best regards
Arno



More information about the linux-mtd mailing list