Re: Bad Blocks On JFFS2/NAND

[Simon Haynes <simon@baydel.com>]

This 5 error business is only if you have relatively new code. Old code 
generates an incorrect and permanent bad block after 1 failure. I am testing 
the suggestion by Thomas that this is a page cache problem by always marking 
an erase page as invalid. No errors as yet but I will keep you posted.

Cheers

Simon.

On Tuesday 19 Oct 2004 10:55 pm, Thomas Gleixner wrote:
> On Tue, 2004-10-19 at 23:45, Michael Moedt wrote:
> > 1. Do you know what usually causes the "Newly-erased block contained
> > word   "... error?
> > Is it caused by a interrupted (or otherwise failed) erase?  Would
> > power-fail cause this?
>
> It's caused by a failed erase. If the chip interface is correct then it
> is usually a problem of a bad page/block. If not (e.g. wrong timing) it
> might return too early from an erase.
>
> > 2. Would this cause good blocks to be incorrectly [and permanently]
> > marked as bad?
>
> Only if failes 5 times after mount. The counter is reset with each
> mount.
>
> > I think I may have seen something similar on my system.  I'm
> > considering writing a test to see if this is a problem for me, but
> > I'd like to learn more about this also.
>
> Which version of the mtd/nand code ?
>
> There was a problem with the page cache, which was not invalidated on
> erase some time ago, but its fixed.
>
> tglx
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/