I could be wrong, but I think JFFS2 uses the OOB. The JFFS2 Out of Band usage section in this link mention about it<br>http://www.linux-mtd.infradead.org/doc/nand.html<br><br>Ceco<br><b><i>Charles Manning &lt;manningc2@actrix.gen.nz&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On Friday 24 November 2006 12:13, goog long wrote:<br>&gt; Thanks for your info, but I have no problem at all with JFFS2 using the<br>&gt; same NAND driver. I run the full test on JFFS2 without any error.<br>&gt;<br>&gt; Ceco<br><br>JFFS2 does not use OOB, so any OOB corruptions don't break JFFS2.<br><br>&gt;<br>&gt; Charles Manning <manningc2@actrix.gen.nz> wrote: This, and all your<br>&gt; previous recent problems, look like issues in the nand driver.<br>&gt;<br>&gt; Allocator out can only happen when a lot of blocks all seem to go bad, or<br>&gt; there are a lot of nand errors.  This is extremely unlikely with
 real<br>&gt; flash, but is quite possible if the software is being told that the blocks<br>&gt; are bad.<br>&gt;<br>&gt; My suggestion is to add more tracing to the lower levels (including the<br>&gt; nand drivers) to figure out what is getting messed up.<br>&gt;<br>&gt; -- CHarles<br></manningc2@actrix.gen.nz></blockquote><br><p>&#32;

<hr size=1>Check out <a href="http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta">the all-new Yahoo! Mail beta</a> - Fire up a more powerful email and get things done faster.