JFFS2 node versioning problem?

[Jörn Engel]

On Wed, 3 May 2006 10:07:22 -0500, Josh Boyer wrote:
> 
> What Artem was asking is if it was physically possible to have a
> file/directory with 4294967296 versions to being with.  Take a 1 byte
> file as an example.  If that was the only file on the whole device,
> and you had that many versions of it you'd have:
> 
> 68 bytes overhead per version + 1 byte of data per version =

68 bytes + 1 byte + 3 bytes padding

> 296352743424 bytes required to store.

309237645312

> That's 276 GiB.  Which isn't even sane for JFFS2 anyway.

Divided by 100k erase cycles:
3.092.376

3MiB is not that insane at all.  Yes, we can theoretically run into
this problem.  But the probability is fairly low.  I'm not too worried
about this.

Jörn

-- 
Measure. Don't tune for speed until you've measured, and even then
don't unless one part of the code overwhelms the rest.
-- Rob Pike