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

David Rees
2001-08-30T02:50:15Z

On Thu, Aug 30, 2001 at 12:05:14PM +1000, Neil Brown wrote:
> On Wednesday August 29, dbr@greenhydrant.com wrote:
> >
> > Now, when you say out-of-memory, do you mean out of memory plus swap? Or
> > just out of memory?
>
> kmalloc(,GFP_NOIO) failure. i.e. transient out-of-phyical-memory
> condition.
> I suspect that kmalloc tends to fail only occasionally as the failure
> will then to slow allocation requests down, and give the VM system a
> bit of time to write more stuff out to disc and so free up memory.
> I am fairly sure that without the patch it will happen again, but
> maybe not straight away.

OK, that explains how it happened, then. Memory had filled up while
copying a good deal of data to the raid partition from another partition.
That must have been when it ran out of memory and hung up.

I'll post again if anything else strange/bad happens.

Thanks,
Dave