From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Bernhard Priewasser <priewasser@gmail.com>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: NOR "bad blocks"
Date: Thu, 27 Oct 2005 10:49:00 +0200 [thread overview]
Message-ID: <20051027084900.GE24422@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <43609066.1010805@gmail.com>
On Thu, 27 October 2005 10:31:34 +0200, Bernhard Priewasser wrote:
>
> So this means that you have to hope that no block will wear out. And
> count on JFFS2's wear levelling.
>From an engineering point of view: yes. With decent wear levelling,
all blocks will roughly wear out at the same time, which you can
calculate beforehand. You need to know your average write rate and
pick a device large enough to support that rate for your target
lifetime.
JFFS2 also has checksums, so when the bitflipping happens, it will get
noticed. But that doesn't mean that it is interpreted as bitflipping.
Most checksum errors are caused by unfinished writes during power
failure.
> What are the reasons that cause NAND blocks to die before they would
> "officially" wear out?
Dunno, not my area of expertise.
> Dou you have a hint for good literature on this stuff (OK, let's better
> say NAND and NOR flash memory in general)?
I'd doubt that there is even decent literature. Stuff is
big-business, but not sexy for research papers. Try finding an
unbiased explanation is such an environment. ;)
Jörn
--
Those who come seeking peace without a treaty are plotting.
-- Sun Tzu
next prev parent reply other threads:[~2005-10-27 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 8:04 NOR "bad blocks" Bernhard Priewasser
2005-10-27 8:21 ` Jörn Engel
2005-10-27 8:31 ` Bernhard Priewasser
2005-10-27 8:49 ` Jörn Engel [this message]
2005-10-27 9:09 ` Bernhard Priewasser
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=20051027084900.GE24422@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=priewasser@gmail.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