Re: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)

Neil Brown (neilb@cse.unsw.edu.au)
Thu, 30 Aug 2001 11:17:37 +1000 (EST)


On Wednesday August 29, dbr@greenhydrant.com wrote:
>
> I'm curious, why hasn't this bug shown up before? Did I just get unlucky?
> Or is everyone else using software raid1 without problems lucky? 8)

You just got lucky.....
This could affect anyone who ran out of free memory while doing IO to
a RAID1 array.
A recent change, which was intended to make this stuff more robust,
probably had the side effect of making the bug more fatal. So it
probably only affects people running 2.4.9.
It could affect earlier kernels, but they would have to sustain an
out-of-memory condition for longer.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/