Re: [Yaffs] Can removing chunkErrorStrikes check cause yaffs…
|This message is part of the following thread:|
|the complete thread tree sorted by date|
|CHEN XUEQIN at|
|CHEN XUEQIN at|
>>>> Here is my question: >>>> 1. Is my patch wrong? >>>> 2. Why the official yaffs2 code assume 3 chunkErrorStrike to >>>> retire a block? Reduce to 1 chunkErrorStrike will wrongly >>>> mark the good block bad? >>>> 3. Should I remove the patch?
>>>> Thanks a lot for your advice. >> Yes, your patch is wrong as any read error will retire the block.
> Thanks for your reply. Now I know patch is wrong. I've read the samsung > nand chip data sheet and anylyse the kernel log. I think so many blocks struck > out are produced by errors in write operation. But it's very strange why those > block went into program error state. According to chip datasheet, if program > operation results in an error, map out the block including the page in error > and copy the target data to another block. Then it's reasonable for yaffs to > retire the block in yaffs_HandleWriteChunkError even if chunk Error Strike count > only be one. But why so many program errors? Any ideas?
> In addition, I used hardware ECC in MTD driver, the error correcting code > is hamming code. The nand chip is MLC mode, so hardware ECC can't correct multi > bit error and mtd return read error to yaffs, this may increase the number or > blocks struck out. I wondered how yaffs handle the uncorrectable bit error in > order to keep filesytem data reliability and integrality. If yaffs2 key data > read from nand is error in some bits, how can yaffs2 work without crash?
|This message was posted to the following mailing lists:|
Mailing List Info | Nearby Messages
|Re: [Yaffs] Can removing chunkErrorStrikes check cause yaffs2 too many Block struck out ?||Re: [Yaffs] Can removing chunkErrorStrikes check cause yaffs2 too many Block struck out ?|
|Stoneboat Mailing List Archive administrated by Jenny||Lurker (version 2.3)|