On 06-09-15 19:22 +0100, Jonathan McDowell wrote:
> On Wed, Sep 13, 2006 at 07:10:10PM +0400, Vitaly Wool wrote:
> > So, the bottom line is the following.
> > I suggest you to try these tests:
> >
> > 1. Create a blank YAFFS filesystem under 2.6.18-git w/ my patch and
> > verify it works (that's what I did recently again :) ). That is,
> > mount, copy, unmount, diff.
> >
> > I hope the flash chip you've got is _not_ with syndrome-based ECC,
> > otherwise ping me for a patch to current nand_base -- it's broken for
> > syndrome case.
>
> Fell at the first hurdle. 2.6.18-rc5 kernel, CONFIG_YAFFS_DOES_ECC is
> not set:
>
> root@balloon2:~$ flash_eraseall /dev/mtd4
> root@balloon2:~$ mount /dev/mtdblock4 /media/mtdblock4
Why is it mtdblock4 BTW? it used to be 1, then it was 2. Have you
repartitioned your nand?
> 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 tragedy: existing chunk < 0 in scan
> (repeat at least 390945 times)
OK. Something is badly wrong here. A useful thing to do to get some
clue what's going wrong is turn on some yaffs tracing. You can do this
live when you have a shell and /proc as described on this page [I've
just made as it didn't appear to be documented anywhere]:
http://www.aleph1.co.uk/yaffsdebugging
> root@balloon2:~$ df -h
> Filesystem Size Used Available Use% Mounted on
> /dev/ram0 7.9M 5.9M 1.6M 78% /
> /dev/ram0 7.9M 5.9M 1.6M 78% /dev/.static/dev
> tmpfs 10.0M 12.0k 10.0M 0% /dev
> /dev/mtdblock4 191.0M 191.0M 0 100% /media/mtdblock4
>
> The flash chips are 3 * K9F1208U0Ms ie 64Mx8 with 512 byte page size
> (which means we're using YAFFS format rather than YAFFS2 I think?).
Correct. 'YAFFS2 in YAFFS compatibility mode'
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
(text/plain)