[patch] Allow any filesystem on MTD Nand when Read Only
panto at intracom.gr
Thu May 6 03:20:25 EDT 2004
Srinivasu.Vaduguri at nokia.com wrote:
>>It's pretty reasonable assumption that bad blocks are created only when
>>writting to NAND. So in the read-only case it is possible to skip over
>>blocks and offer a bad-block free block device to the upper layers.
>>This allows us to utilize any filesystem when read-only.
>I had seen in the past that there can be bit errors (more than one bit) when we do
>multiple reads (probably many) on the same block. So we will read corrupted data from NAND flash and we will not be able to decompress the data when using the CRAMFS. If we erase the block and rewrite the data, it works fine. This is my experience with a samsung NAND flash.
>So using this above logic how will we detect if there are more than one bit errors while reading. Can we afford to rewrite the cramfs image again onto the NAND flash ?
>Please tell me if I got this problem because of any obvious mistake.
Hmm, that's the first time I've heard about this problem.
But if you have read errors, how can you be sure that you will be able
to read the
block and write it somewhere else?
Maybe you can do something when writting your filesystem image when you
a simple bit error you can immediately mark the block bad.
How many times have you written the block in order for something like
this to occur?
It seems to me that when you have a read only partition the solution is
carefull when writting your filesystem image.
First you avoid the bad block altogether, and secondly you always bit verify
the block. If the verify fails you immediately mark the block as bad and
I don't think that nandwrite does it though.
More information about the linux-mtd