From: Pantelis Antoniou <panto@intracom.gr>
To: tglx@linutronix.de
Cc: Srinivasu.Vaduguri@nokia.com
Cc: dwmw2@infradead.org
Cc: linux-mtd@lists.infradead.org
Cc: ddaney@avtrex.com
Subject: Re: [patch] Allow any filesystem on MTD Nand when Read Only
Date: Thu, 06 May 2004 12:45:17 +0300 [thread overview]
Message-ID: <409A092D.1060505@intracom.gr> (raw)
In-Reply-To: <200405061148.24573.tglx@linutronix.de>
Thomas Gleixner wrote:
>On Thursday 06 May 2004 11:30, Srinivasu.Vaduguri@nokia.com wrote:
>
>>>How many times have you written the block in order for something like
>>>this to occur?
>>>
>>I haven't counted the number of times. But I remember reading some
>>information, that even on multiple reads we do get bit errors and it is a
>>symptom that the block slowly becoming bad after some time.
>>
>
>Hmm. Never seen this. I have some read only paritions which are accessed in
>stress testing and I never have seen, that a block gets bad due to reading.
>
>
>>But what I feel is, a read-only filesystem like cramfs is not that reliable
>>on NAND flash. We have to detect a bad block early.
>>
>
>Yep, but you can only detect it while writing / erasing.
>
>
Actually when using ECC you *CAN* detect a single bit error.
You could use this information as a trigger to migrate the block
and then mark it bad immediately.
However it better be only one bit that flipped because if more
bits are gone you're screwed.
Regards
Pantelis
next prev parent reply other threads:[~2004-05-06 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AEB09EDA2548094C81ED6AA93269F63D01D09323@siebe001.apac.nokia.com>
2004-05-06 9:39 ` [patch] Allow any filesystem on MTD Nand when Read Only Pantelis Antoniou
2004-05-06 9:48 ` Thomas Gleixner
2004-05-06 9:45 ` Pantelis Antoniou [this message]
[not found] <AEB09EDA2548094C81ED6AA93269F63D01D09322@siebe001.apac.nokia.com>
2004-05-06 7:20 ` Pantelis Antoniou
2004-05-06 8:02 ` Thomas Gleixner
2004-05-05 12:33 Pantelis Antoniou
2004-05-05 12:57 ` David Woodhouse
2004-05-05 13:03 ` Pantelis Antoniou
2004-05-05 15:26 ` David Daney
2004-05-05 17:44 ` Phillip Lougher
2004-05-05 19:07 ` David Daney
2004-05-06 7:12 ` Pantelis Antoniou
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=409A092D.1060505@intracom.gr \
--to=panto@intracom.gr \
--cc=Srinivasu.Vaduguri@nokia.com \
--cc=tglx@linutronix.de \
/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