UBI/UBIFS issue: corrupt empty space => switched to read-only mode
dedekind1 at gmail.com
Tue Mar 20 06:39:43 EDT 2012
On Fri, 2012-03-16 at 17:14 +0100, Matteo Mattei wrote:
> Hi guys,
> I am working hard on UBIFS to make it works on 2.6.32 and OMAP3530.
> I already posted some requests to TI forum but I have no answers up to now:
Well, this error was reported several times. AFAIR, there are 2 possible
causes for this.
1. Your driver does not protect the empty space. Normally the driver
corrects bit-flips using ECC, but some systems do not do this for empty
space, i.e., for the flash regions which have been erased but have never
been written. UBIFS expects to see all 0xFFs there, and if it doesn't,
it reports about corrupt empty space.
You can fix this by fixing the driver, at least this is what people seem
to do. If this is impossible to fix, you can teach UBIFS to tolerate
bit-flips in the empty space.
2. More difficult issue which no one still dares to start fixing is the
unstable bits issue. I do not have time to work on this, so I offer
everyone assistance, but no on so far started working on this, AFAIK.
Here is the description of the issue:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the linux-mtd