Date: Wed, 24 Jun 2009 11:44:34 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: freebsd@t41t.com Cc: FreeBSD-Questions@freebsd.org Subject: Re: you're not going to believe this. Message-ID: <alpine.BSF.2.00.0906241141410.63537@wojtek.tensor.gdynia.pl> In-Reply-To: <20090624093223.GF3468@ece.pdx.edu> References: <20090622230729.GA20167@thought.org> <a9f4a3860906231222r65faaf1cia6b68186c79f4791@mail.gmail.com> <20090623201041.GA23561@thought.org> <20090623205944.GA43982@Grumpy.DynDNS.org> <20090624010922.GA24335@thought.org> <20090624093223.GF3468@ece.pdx.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> First, be careful about statements like "10 years before it fails to hold > state." Usually that means if you write data to the device and put it on a > shelf, you've got 10 years before the data is unreadable. Being marketing possibly it's true if you will write it few times and no more ;) store it in perfect stable room temperature with low natural radiation background etc. > for a decade? The number you probably care about is how long _in active > use_ the drive will last, and that's probably _not_ 10 years. The primary 10000 writes of it's size if it would be properly managed (flash filesystem). As it emulates disk divide it by at least two on writing large files, at least 20 in case of random small writes. > is less noticeable. Implementing wear leveling in OS-level software > isn't feasible. As I mentioned, wear leveling happens within the chip, > so the OS doesn't even know a block swap has occurred. (As an extension you are wrong. flash chips doesn't do this. There is a controller that do this. If it would give simple interface to flash chips and say PCI-Express or SATA, making proper flash filesystem would be possible.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0906241141410.63537>