From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
linux@horizon.com, kalin@thinrope.net,
linux-kernel@vger.kernel.org
Subject: Re: Lifetime of flash memory
Date: Mon, 27 Mar 2006 13:01:45 -0500 [thread overview]
Message-ID: <20060327180145.GD16773@csclub.uwaterloo.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0603271242100.16721@chaos.analogic.com>
On Mon, Mar 27, 2006 at 12:44:50PM -0500, linux-os (Dick Johnson) wrote:
> Experimental data show that it is not possible to 'destroy' the
> chip by interrupting a write as previously reported by others.
> In fact, one of the destroyed devices was recovered by writing
> all the sectors in the device as in:
> `dd if=/dev/zero of=/dev/hdb bs=1M count=122`.
I have a destroyed card here. And I tried doing that. A rep from
sandisk told me, that yes that model/generation of sandisk could
encounter that situation where the device was simply impossible to
access because of corruption during a write. He also said the card
would have to be sent back to the factory to have the table reset.
Newer generations were going to fix that so it didn't happen again.
> Note that there __is__ a problem that may become a "gotcha" if
> you intend to RAW copy devices, one to another, for production.
> The reported size (number of sectors) is different between
> devices of the same type and manufacturer! Apparently, the size
> gets set when the device is tested.
Yeah, I load cards by partitioning, mkfs'ing, and extracting data.
Different manufacturers almost never have the same excact size.
Len Sorensen
next prev parent reply other threads:[~2006-03-27 18:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 7:49 linux
2006-03-26 13:55 ` Artem B. Bityutskiy
2006-03-26 16:21 ` linux
2006-03-26 16:36 ` Artem B. Bityutskiy
2006-03-27 16:18 ` Lennart Sorensen
2006-03-27 17:44 ` linux-os (Dick Johnson)
2006-03-27 18:01 ` Lennart Sorensen [this message]
2006-03-28 4:28 ` Sergei Organov
2006-03-28 6:41 ` Magnus Damm
2006-03-28 8:58 ` Sergei Organov
2006-03-28 12:55 ` linux-os (Dick Johnson)
2006-03-28 13:27 ` Sergei Organov
2006-03-28 13:35 ` Sergei Organov
2006-03-29 1:01 ` linux
2006-03-29 4:33 ` Sergei Organov
2006-03-29 15:56 ` linux
2006-03-30 6:33 ` Sergei Organov
2006-03-30 11:23 ` linux
2006-03-30 12:18 ` Sergei Organov
2006-03-28 0:21 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 17:01 John Richard Moser
2006-03-21 17:14 ` David Vrabel
2006-03-21 17:28 ` John Richard Moser
2006-03-21 18:37 ` Paulo Marques
2006-03-21 18:00 ` hackmiester / Hunter Fuller
2006-03-21 18:20 ` Joshua Kugler
2006-03-21 18:40 ` John Richard Moser
2006-03-23 3:46 ` Kalin KOZHUHAROV
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060327180145.GD16773@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=dedekind@yandex.ru \
--cc=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=linux@horizon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome