--- In "Don W. Carr" <> wrote:
> We need to create a HOWTO for doing datalogging to flash memory.
Even if you
> had to buy new SD cards every five years, it might still be cheaper
and more
> reliable than purchasing a mini hard drive.
>
> Don.
This is exactly what we've found. The super-miniaturized mechanical
guts of a microdrive do not lend themselves well to high MTBF. They
use a lot of power and run hot being so small. The intended workload
has a very small duty-cycle as they are designed to be powered off and
idle most of the time.
SD and CF have internal bad block management and wear leveling
algorithms that go on in the controller of the card itself. Those
electronics make traditional filesystems like FAT or EXT2 no so bad on
flash. Also, not many people can argue that modern SD or CF running
EXT2 or EXT3 is too slow anymore-- the hardware ASICs on the CF/SD
cards are quite fast and effective at what they do.
JFFS2 and YAFFS couple the bad block management and wear leveling to
the filesystem design itself which is partially the reason their scope
is limited to a particular type of raw flash chip technology (nand,
nor, 2k page nand, etc...). The methodology of a flash translation
layer underneath a standard block filesystem and the good algorithms
for it are mostly protected from GPL/Linux implementation by a patent
minefield and the perceived opportunity for speed and design
perfection by coupling the two distinct tasks (wear leveling/bad block
management and UNIX filesystem) together in one uber-filesystem.
//Jesse Off
------------------------ Yahoo! Groups Sponsor --------------------~-->
Everything you need is one click away. Make Yahoo! your home page now.
http://us.click.yahoo.com/AHchtC/4FxNAA/yQLSAA/CFFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|