From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Lifetime of flash memory
Date: Thu, 23 Mar 2006 12:46:44 +0900 [thread overview]
Message-ID: <dvt5l0$413$1@sea.gmane.org> (raw)
In-Reply-To: <44203179.3090606@comcast.net>
John Richard Moser wrote:
> I have a kind of dumb question. I keep hearing that "USB Flash Memory"
> or "Compact Flash Cards" and family have "a limited number of writes"
> and will eventually wear out. Recommendations like "DO NOT PUT A SWAP
> FILE ON USB MEMORY" have come out of this. In fact, quoting
> Documentation/laptop-mode.txt:
>
> * If you're worried about your data, you might want to consider using
> a USB memory stick or something like that as a "working area". (Be
> aware though that flash memory can only handle a limited number of
> writes, and overuse may wear out your memory stick pretty quickly.
> Do _not_ use journalling filesystems on flash memory sticks.)
I thought that journaling filesystems happen to overwrite exactly the same
place (where the journal is) many times... Am I mistaken?
So the effect is what we had for floppies (some many years ago) where sector
0 and others where FAT structure was kept were overused and start giving
errors - so the only solution was to throw away that floppy.
Hard disks had the same problem, but they have algorithms to relocate bad
clusters.
So do these "leveling algorithms" refer to the same? Relocating bad cells?
If not, you can see how a journaling system can fry a CF card quickly.
>
> The question I have is, is this really significant? I have heard quoted
> that flash memory typically handles something like 3x10^18 writes; and
> that compact flash cards, USB drives, SD cards, and family typically
> have integrated control chipsets that include wear-leveling algorithms
> (built-in flash like in an iPaq does not; hence jffs2). Should we
> really care that in about 95 billion years the thing will wear out
> (assuming we write its entire capacity once a second)?
>
> I call FUD.
3x10^18 is a bit overstating, IMHO. Don't have a reference now.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2006-03-23 3:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:01 Lifetime of flash memory 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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='dvt5l0$413$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
/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