Quoting Gilad Ben-Yossef, from the post of Thu, 17 May:
The tool would be useless. The underlying flash (probably NAND technology)
storage works in erase blocks sizes, each of which can be written x (for
value of x somewhere around 100,000 writes) before it becomes unreliable.
The more
I have a flash card which I suspect has a defect. every time I go out
and take photos with it, at least one image file comes back corrupted.
to make sure it's not the cammera or something else, I thought it would
be nice to have a memtest-like tool that wrote patterns and tried to
read them again,
Ira Abramov wrote:
I have a flash card which I suspect has a defect. every time I go out
and take photos with it, at least one image file comes back corrupted.
to make sure it's not the cammera or something else, I thought it would
be nice to have a memtest-like tool that wrote patterns and
On Thu, May 17, 2007, Gilad Ben-Yossef wrote about Re: running testing
patterns on block devices:
The more writes, the lesser the useful life expetency. To combat this the
Compact Flash hardware does something called uses a wear leveling
algorithm to virtualize the low level sectors the OS
Nadav Har'El wrote:
On Thu, May 17, 2007, Gilad Ben-Yossef wrote about Re: running testing patterns on
block devices:
The more writes, the lesser the useful life expetency. To combat this the
Compact Flash hardware does something called uses a wear leveling
algorithm to virtualize the low
On Thu, May 17, 2007 at 11:06:35AM +0300, Nadav Har'El wrote:
I have a question unrelated to the original question (and to Linux...):
How does this wear leveling work if a card is mostly full? E.g., my
typical situation is that I have a 512 MB card, but 450 MB of it is full
(with pictures I
