Re: mkfs.jffs2 min erase block size: 4 vs 8 KiB

[Artem Bityutskiy <dedekind1@gmail.com>]

On Wed, 2011-06-22 at 01:02 -0400, Mike Frysinger wrote:
> the current mkfs.jffs2 util has in its --eraseblock handling:
> /* If it's less than 8KiB, they're not allowed */
> if (erase_block_size < 0x2000) {
>     fprintf(stderr, "Erase size 0x%x too small. Increasing to 8KiB minimum\n",
>         erase_block_size);
>     erase_block_size = 0x2000;
> }
> 
> but i cant seem to find documentation on where this comes from.  it's
> not uncommon to have SPI flashes with 4KiB erase sectors, and removing
> this sanity check and allowing 4 KiB seems to produce an image that
> works OK.
> 
> am i missing something ?  or should i send a patch to drop this check ?

I do not believe JFFS2 is able to work with such small erase blocks. In
JFFS2 (and in UBIFS as well) an eraseblock is the basic garbage
collection unit, and nodes cannot cross eraseblock boundaries. And the
maximum node size is 4KiB of data plus few bytes of node header. So 4KiB
won't even fit the largest data node, e.g., containing uncompressible
data.

Even 8KiB is bad, because the amount of wasted space will be large -
JFFS2 will waste the rest of the eraseblock if it does not fit the node.
So the smaller EB is, the more wasted space you have.

For SPI flashes the way out is to emulate larger eraseblock sizes on MTD
level. I'd recommend at least 32 KiB.

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)