On Mon, Sep 24, 2007 at 10:07:35AM -0400, ian@brightstareng.com wrote:
> On Sunday 23 September 2007 17:15, Jonathan McDowell wrote:
> > This is just a minor addition; the trace message for when
> > yaffs marks a block bad doesn't have a newline on the end
> > which causes output like:
> >
> > nand_erase: attempt to erase a bad block at page 0x000223e0
> 
> This doesn't look right - yaffs should not be erasing bad-blocks.
> If the block just turned bad AND it got marked bad in MTD then
> this might happen - but i don't think that's likely, and most MTD
> setups don't have dynamic (mtd) bad-block-list update.  This is
> probably an indicator of some other issue, perhaps not reading
> the true blockState during initial scan.

It appears to give the same errors every time the FS is mounted, so
something does seem to be going wrong. For the moment I've dropped back
to JFFS2 which is working fine on the same device.

J.

-- 
Programmer, | I'd love to but... I'm having all  |       Tel/SMS:
sysadmin &  |        my plants neutered.         |   +423-663-212343
BHMF.       |                                    |  Made by HuggieTag