--- In Jason Stahls <> wrote:
>
> j.chitte wrote:
> > I'm a little hesitant to use ignoreBB until I have a strategy for detecting
> > the truly bad blocks. This fault itself will surely have produced some burn
> > out as fewer blocks were available. Some process needs to be run to prevent
> > arbitrary file errors occuring due to marking real bad blocks as good.
>
> How about opening the block device and writing to it till it's full then
> format the flash again without the ignoreBB? Or use mkfs to create a
> ext2 filesystem and have it check for bad blocks, then switch back to
> yaffs or jffs.
>
> --
> Jason Stahls
>
Hi Jason,
am I right in thinking you're suggesting doing all that after an initial
ersase_all_ignoreBB ?
IIRC the erased state if FF so I should write a series of 00 . To save this
operation doing excessive writing as well I should try to write 2k files. Or
could I dd to the block device?
dd if=/dev/zero of=/mnt/mtdblock1 bs=2048
I don't want to do something stupid that will burn the device for real through
lack of knowledge of the low level operations and the NAND flash chips. Neither
do I have the time to become a flash developer just to sort out this mess.
Do you think ext2 bad block check not going to hammer part of the device? IFAIK
there's no load spreading mechanism.
thanks for your ideas.
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|