j, when I ran into this a year or so ago I did some google searches on yaffs and lots of interesting things come up about it. Suffice it to say that we switched to jffs2 shortly thereafter and have had zero issues. I've fielded lots of high reliability systems using jffs2 with good success. I'm sure that yaffs has better performance in some cases but what good is it if it's not reliable? jffs2 it is for us for the foreseeable future.
Also, FWIW I have not tried the fix from technologic for the bad block issue, but we attempted the same thing here; we modified mtdutils flash_eraseall and the kernel to make them ignore bad blocks and we couldn't get them to clear. Maybe our code was wrong. I would like to recover our 3 broken TS-7250s someday so hopefully the technologic code will fix it.
Best of luck.
Gary Wicker
qhorus.com
On Sat, Aug 15, 2009 at 4:24 AM, j.chitte <m("yahoo.com","j.chitte");">> wrote:
OK , I have managed to set up a basic 2.6 + yaffs2 system on nfs and boot it.
I can mount /dev/mtdblock1 although it remains pretty "tragic" I can login to console and list the files.
# mount -t yaffs /dev/mtdblock1 /mnt/mtd1
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs: auto selecting yaffs2
block 912 is bad
block 980 is bad
block 987 is bad
block 988 is bad
block 989 is bad
**>> Block 986 needs retiring
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs_read_super: isCheckpointed 0
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 73332456 43663748 29668708 60% /
tmpfs 64 0 64 0% /dev
/dev/mtdblock1 128000 45024 82976 35% /mnt/mtd1
# ls /mnt/mtd1
bin etc initrd mnt sbin var
busyhack fastboot lib proc tmp www
dev home lost+found root usr
The mount process takes the normal few seconds that a yaffs2 mount should take. The file usage is about what is should be:
# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 69.9G 41.6G 28.3G 60% /
tmpfs 64.0K 0 64.0K 0% /dev
/dev/mtdblock1 125.0M 44.0M 81.0M 35% /mnt/mtd1
But it's impossible to do much with it...
# ls -l /mnt/mtd1/tmp/nano
-rw-r--r-- 1 507 507 108476 Jan 23 2008 /mnt/mtd1/tmp/nano
# rm -f /mnt/mtd1/tmp/nano
rm: cannot remove '/mnt/mtd1/tmp/nano': Directory not empty
In short yaffs2 is looking pretty sucky as a fs choice.
I need to get a ftp server on this set up to grab an image and restort the fs later after blasting the fs with erase_all_ignoreBB
yaffs , yet another fuckey file system. Not impressed.
__._,_.___
![]()
__,_._,___
|