On Fri, Jun 25, 2004 at 07:46:48AM +1000, Neil Brown wrote:
> > Are there any MD code changes that could have caused this so I can point
> > SuSE somewhere? (Well, then again, many SuSE folks are on this list
> > anyway...)
> 
> This is definitely a bug in the Suse 2.6.4-52 kernels, and I'm pretty
> sure they have fixed it.

Thanks, I upgraded the box to 2.6.5-7.75-smp and the bug has vanished.

-- 
Joshua Kwan