linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rees <dbr@greenhydrant.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)
Date: Wed, 29 Aug 2001 19:50:06 -0700	[thread overview]
Message-ID: <20010829195006.B23371@greenhydrant.com> (raw)
In-Reply-To: <20010829144016.C20968@greenhydrant.com> <3B8D6BF9.BFFC4505@zip.com.au> <20010829153818.B21590@greenhydrant.com> <3B8D712C.1441BC5A@zip.com.au> <20010829155633.D21590@greenhydrant.com> <15245.35636.82680.966567@notabene.cse.unsw.edu.au> <20010829175541.E21590@greenhydrant.com> <15245.37937.625032.867615@notabene.cse.unsw.edu.au> <20010829182406.A23371@greenhydrant.com> <15245.40794.888447.345100@notabene.cse.unsw.edu.au>
In-Reply-To: <15245.40794.888447.345100@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Thu, Aug 30, 2001 at 12:05:14PM +1000

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

      reply	other threads:[~2001-08-30  2:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29 20:17 kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?) David Rees
2001-08-29 20:47 ` Andrew Morton
2001-08-29 21:14   ` David Rees
2001-08-29 21:38     ` Andrew Morton
2001-08-29 21:40       ` David Rees
2001-08-29 22:26         ` Andrew Morton
2001-08-29 22:38           ` David Rees
2001-08-29 22:48             ` Andrew Morton
2001-08-29 22:56               ` David Rees
2001-08-30  0:39                 ` Neil Brown
2001-08-30  0:55                   ` David Rees
2001-08-30  1:17                     ` Neil Brown
2001-08-30  1:24                       ` David Rees
2001-08-30  2:05                         ` Neil Brown
2001-08-30  2:50                           ` David Rees [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010829195006.B23371@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).