public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jared Hulbert <jaredeh@gmail.com>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	MTD List <linux-mtd@lists.infradead.org>
Subject: Re: CRC on Read-Only partition
Date: Wed, 19 Jan 2005 11:46:16 -0800	[thread overview]
Message-ID: <6934efce05011911462552f555@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0501191648070.8174@phoenix.infradead.org>

> The question is: if we've read page and encounter ECC error, is it
> possible that if we re-read it several times we will have no errors? This
> means does NAND technology assume random occasional bit flips which go
> away after we re-read page?

Whether or not the error goes away was not the point.  My point is
that with NAND you can get errors even with RO data.  That's all.
 
> P.S. :
> Toshiba's guide stands bit flipping is possible, but they stay until block
> is erased. Re-read as many times as yiu want - you will still have this
> bit error. But this doesn't mean block is bad - erase the block and be
> happy.

I think the real question is whether the likelyhood of errors getting
past the NAND's ECC is > or < than the users tolerance level.  I don't
believe that the answer should be terribly different for RO or RW
data.  Yet this depends on temperature, frequency of read, and yes
even solar flares :)  Therefore the answer is different for a set top
box with an expected useful life of 2 years and a car.

      reply	other threads:[~2005-01-19 19:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 12:25 CRC on Read-Only partition Artem B. Bityuckiy
2005-01-13 12:31 ` David Woodhouse
2005-01-13 13:18   ` Artem B. Bityuckiy
2005-01-18 18:01     ` Jared Hulbert
2005-01-19 13:09       ` Artem B. Bityuckiy
2005-01-19 16:56         ` Artem B. Bityuckiy
2005-01-19 19:46           ` Jared Hulbert [this message]

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=6934efce05011911462552f555@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --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