> > ps -aux | grep loop
> 1674 tty1 DW< 0:00 [loop0]
> The system is doing nothing to the loop filesystem.
> Strange that the process isn't logging any cpu usage time. It's
> definately responsible for the 1.00 load.
It's just an artifact of the fact that processes in state D
(uninterruptible sleep) are included in the load average calculation.
Since the loop thread apparently sits in state D waiting for events
on its device, you get a load average of 1 for each mounted loop
I know nothing about the implementation of the loop thread so won't
presume to say whether/how it can be "fixed".
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/