lkml.org 
[lkml]   [2001]   [Aug]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)
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.


NeilBrown

>
> Running out of memory is quite common with the kernel always filling up
> buffers and cache, but running out of memory+swap is not common (and I know
> I didn't hit that in my setup!)
>
> Thanks for your help,
>
> -Dave
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:01    [W:0.305 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site