On Tue, Sep 12, 2006 at 04:23:11PM +0400, Vitaly Wool wrote:
> On 9/12/06, Jonathan McDowell <noodles@earth.li> wrote:
> >Should I expect this to work on filesystem that works fine on 2.6.16.5
> >(in particular 2.6.16.5-tcl1 on a Balloon2)?
>
> I think you should. If that is not the case, please let me know, let's
> debug that together :)
Ok. I've got a bit further with is. If I enable CONFIG_YAFFS_DOES_ECC
in my 2.6.18-rc5 build (it was enabled in the 2.6.16.5) then I can at
least mount and boot from the yaffs partition. I'm a bit surprised by
this - YAFFS and MTD handle ECC usage differently?
However although I can boot I still get lots of errors:
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
block 4320 is bad
block 7547 is bad
block 8136 is bad
block 10184 is bad
**>>yaffs ecc error fix performed on chunk 34:0
**>>Block 1 marked for retirement
**>>yaffs ecc error fix performed on chunk 35:1
**>>Block 1 marked for retirement
**>>yaffs ecc error fix performed on chunk 36:0
**>>Block 1 marked for retirement
**>>yaffs ecc error fix performed on chunk 37:0
**>>Block 1 marked for retirement
**>>yaffs ecc error fix performed on chunk 42:0
**>>Block 1 marked for retirement
and many more; full bootlog at:
http://the.earth.li/~noodles/balloon2-yaffs-boot.log
These errors seem consistent over boots - certainly a subsequent boot
has exactly the same chunks/blocks listed for the first dozen or so
errors (I didn't check the rest).
J.
--
Have you been having any immoral | .''`. Debian GNU/Linux Developer
thoughts lately? I know I sure | : :' : Happy to accept PGP signed
have. | `. `' or encrypted mail - RSA +
| `- DSA keys on the keyservers.
(text/plain)