public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Bernhard Priewasser <priewasser@gmail.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: NOR "bad blocks"
Date: Thu, 27 Oct 2005 10:31:34 +0200	[thread overview]
Message-ID: <43609066.1010805@gmail.com> (raw)
In-Reply-To: <20051027082108.GC24422@wohnheim.fh-wedel.de>

> Not easily.  I haven't done the experiments myself, but wear-out
> effects were described to me.  Basically, you can write to a block and
> read it back out in a tight loop and things will never fail.  Not
> after 100k, not after 1M erases.  But if you write to the block and
> wait long enough, bits will flip.
> 
> Bit-flipping will always happen from 0 to 1, similar to erases.
> Problem should be that the insulation around a flash cell has eroded
> and the charge will leak out over time - this cell is self-erasing
> now.

So this means that you have to hope that no block will wear out. And 
count on JFFS2's wear levelling.

What are the reasons that cause NAND blocks to die before they would 
"officially" wear out?
Dou you have a hint for good literature on this stuff (OK, let's better 
say NAND and NOR flash memory in general)?

-- 
Bernhard

  reply	other threads:[~2005-10-27  8:31 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 [this message]
2005-10-27  8:49     ` Jörn Engel
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=43609066.1010805@gmail.com \
    --to=priewasser@gmail.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.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