need arguments to use JFFS2

[David Woodhouse]

thlang at iphase.com said:
> Please could someone give me some arguments to use JFFS2 instead of
> all others Flash FS such as CRAMFS ? 

cramfs is read-only. If you don't want to write to your file system, you 
should probably be using it instead of JFFS2. 

The only other flash file system for Linux is YAFFS, for use on NAND flash.
I don't know as much about YAFFS as I should -- the choice between YAFFS and
JFFS2 on NAND is basically a tradeoff between the improved speed and mount
time of YAFFS, and the increased storage capacity which JFFS2 compression 
gives, I think. Charles will probably offer more enlightenment.

Other than that, you only have the brain-dead 'translation layer' crap which
is a kind of journalling pseudo-filesystem used to emulate a virtual hard
drive, on which you need to use put a 'normal' journalling file system. This
two-layer approach made some sense in the days of DOS, where you could just
provide an INT 13h Disk BIOS IRQ handler and pretend to be a normal hard
drive to DOS, but it makes far less sense now. You end up with power-loss
safety being implemented in _both_ your 'normal' file system and the
underlying pseudo-fs, the pseudo-fs has no way of knowing which blocks on
the virtual hard drive are marked as 'free' by the higher file system and so
it keep garbage-collecting stale data from one place on the flash to
another, and at least at the moment, it means you don't get compression --
although that's not a fundamental design flaw like the others. 


--
dwmw2