Re: flash file system for production use

[Michael Palme <m.palme@goepel.com>]

okay... thanks for the answer.
i will do some serious testing myself. what would be a real life 
scenario ??? is a random loop with creating, writing and deleting files 
mixed with mounting and unmounting and some random powerfaults???

i think the salesdroids- thing will not work: they only thing they want 
is to get a product to the market as fast as they can...

David Woodhouse schrieb:

>m.palme@goepel.com said:
>  
>
>> i need a  mechanism for storing configuration files etc in the
>>flashes. for this  purpose 20mb of the flashes are free. the
>>performance/ stability thing  is very important for me. i cant wait 10
>>secs fot mounting/ checking  etc. i' ve tried jffs2 from CVS and it
>>seems to be "fast" on a nearly  empty flash partition, but i have no
>>suggestion about what happens in  hard production use, when the flash
>>will be written  over and over again  and the wear leveling takes
>>place. the device is never shutdown'ed in a  clean way -- always hard
>>power off... 
>>    
>>
>
>JFFS2 from CVS should be fine. It hasn't had as much hard testing as the
>stable branch, but I have no particular reason to expect it to be broken on
>NOR flash. I wouldn't ship it to a customer before doing some serious
>retesting, but you can do that yourself and report anything you find -- I
>don't expect anything to break.
>
>There are other things we can do to improve performance and mount time even
>more than we've already done in CVS. They're listed in the TODO file, and if
>you're likely to actually implement them I'm happy to give more explicit
>pointers -- or I can set our salesdroids on you if that would be useful :)
>
>--
>dwmw2
>
>  
>