ts-7000
[Top] [All Lists]

Re: [ts-7000] Re: Microdrive / Type II CF?

To:
Subject: Re: [ts-7000] Re: Microdrive / Type II CF?
From: "Don W. Carr" <>
Date: Thu, 1 Jun 2006 21:54:53 -0500
Ok, I plan to buy a 2 Gig SD card for data logging, which should take at least 6 months to fill at one sample per second while the train is running. I did not realize that the SD and CF cards had internal electronics for wear leveling and bad block management. What is the best file system to use? I would think ext3 might be a good option. Don.

On 6/1/06, Jesse Off <> wrote:
--- 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






SPONSORED LINKS
Linux os Hardware Arms
Computer internet Computer security Computer hardware security


YAHOO! GROUPS LINKS

  •  Visit your group "ts-7000" on the web.
     
  •  To unsubscribe from this group, send an email to:
     =Unsubscribe
     
  •  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.





--
Dr. Don W. Carr
J. G. Montenegro 2258
Guadalajara, Mexico
+52-333-630-0704
+52-333-836-4500 ext 2930

SPONSORED LINKS
Linux os Hardware Arms
Computer internet Computer security Computer hardware security


YAHOO! GROUPS LINKS

  •  Visit your group "ts-7000" on the web.
     
  •  To unsubscribe from this group, send an email to:
     =Unsubscribe
     
  •  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU