From: David Rees <dbr@greenhydrant.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
ext3-users@redhat.com
Subject: Re: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)
Date: Wed, 29 Aug 2001 14:40:16 -0700 [thread overview]
Message-ID: <20010829144016.C20968@greenhydrant.com> (raw)
In-Reply-To: <20010829131720.A20537@greenhydrant.com> <3B8D54F3.46DC2ABB@zip.com.au>, <3B8D54F3.46DC2ABB@zip.com.au>; <20010829141451.A20968@greenhydrant.com> <3B8D60CF.A1400171@zip.com.au>
In-Reply-To: <3B8D60CF.A1400171@zip.com.au>; from akpm@zip.com.au on Wed, Aug 29, 2001 at 02:38:23PM -0700
On Wed, Aug 29, 2001 at 02:38:23PM -0700, Andrew Morton wrote:
>
> OK, thanks. bdflush is stuck in raid1_alloc_r1bh() and
> everything else is blocked by it. I thought we fixed
> that a couple of months ago :(
>
> Could you send the output of `cat /proc/meminfo'?
>
> > 18239 -bash wait4
> > 18274 umount /opt rwsem_down_write_failed
>
> What are we trying to do here? Is /opt the deadlocked
> filesytem?
Yep, /dev/md0 is mounted on /opt.
-Dave
next prev parent reply other threads:[~2001-08-29 21:40 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 [this message]
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
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=20010829144016.C20968@greenhydrant.com \
--to=dbr@greenhydrant.com \
--cc=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.