ubifs_scan: corrupt empty space

[nick]

On 2015-06-27 04:11 PM, Richard Weinberger wrote:
> On Fri, Jun 26, 2015 at 4:31 PM, Brian Hill <brian at houston-radar.com> wrote:
>>
>> One of our systems using Atmel ARM A5, Micron MT29F4G08ABADAWP -w- kernel 3.17 produced this error, which proved unrecoverable:
>>
>> UBIFS error (pid 452): ubifs_scan: corrupt empty space at LEB 2670:125358
>> UBIFS error (pid 452): ubifs_scanned_corruption: corruption at LEB 2670:125358
>> UBIFS error (pid 452): ubifs_scanned_corruption: first 1618 bytes from LEB 2670:125358
>> 00000000: fffffffd ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
>>
>> There have been various threads on this type of error over the years, such as:
>> http://lists.infradead.org/pipermail/linux-mtd/2012-January/039254.html
>>
>> The most notable comment being:
>>
>>> ubifs expect empty space to be protected by ecc. But if empty page ecc is not
>>> ff, this need hack in the nand driver.
>>
>> I find that no, the atmel driver, unlike some others, doesn't attempt to "correct" erased pages which contain bit flips.
>> Is the driver still the preferred place to address this issue?  What if the erased space has more bit flips than the ECC strength of the device?  It seems like that block should simply be retired - it has no actual user data.  Will UBIFS handle this particular condition?
> 
> UBIFS assumes that an empty page contains only 0xFFs.
> On modern NAND chips, especially MLC, this seems no longer to be the case.
> 
> So far no generic solution was found.
> Please see:
> http://lists.infradead.org/pipermail/linux-mtd/2014-March/052521.html
> and
> http://lists.infradead.org/pipermail/linux-mtd/2014-March/052507.html
> 
Richard,
There seem to be a lot of messages related to unfixed/issues with ubifs and current 
flash hardware. I was wondering if we can either write better documentation on the
mtd wiki for this or even better in the kernel Documentation directory to help save
you some time with answering these common questions now. :) Unfortunately I am not
aware of all the issues so letting someone else to write the Docs is better. 
Nick