No clean _or_ dirty blocks to GC from!

David Woodhouse dwmw2 at
Fri Oct 5 09:12:34 EDT 2001

ldoolitt at said:
>  Possibilities:
> 1. Change nothing.  The software doesn't get confused, just the
> operator.

Works for me :) But probably not the right thing to do :)

> 2. Add code to avoid the printk's when there are plenty of _free_
> blocks.

Seems sane, if it's necessary. Probably just downgrade it to a debugging 

> 3. Don't trigger the GC on mount unless there is something to do. 

The first thing the thread does on mount is sleep anyway. I'm not sure why 
it's getting woken.


More information about the linux-mtd mailing list