Fw: corrupt my NAND flash device

Jörn Engel joern at wohnheim.fh-wedel.de
Tue Apr 22 16:59:05 EDT 2003


On Tue, 22 April 2003 22:26:27 +0200, Jörn Engel wrote:
> 
> Agreed. But this problem should be handled in kernel. In other words,
> the writing process has to trigger GC and continue writing, if GC
> managed to free more space. It would make sense to tell GC, how much
> space is needed, so it won't work over the whole device, locking the
> NAND for a long time.
> 
> Anything else is very unintuitive to the user and a plain bug, at
> least in my book.

BTW: See the thread "Does jffs2 garbage collection include erasing"

jffs2 does just this. And I didn't even know the code until a few
minutes ago. :)

Jörn

-- 
My second remark is that our intellectual powers are rather geared to
master static relations and that our powers to visualize processes
evolving in time are relatively poorly developed.
-- Edsger W. Dijkstra



More information about the linux-mtd mailing list