From: David Rees <dbr@greenhydrant.com>
To: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
ext3-users@redhat.com
Subject: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)
Date: Wed, 29 Aug 2001 13:17:20 -0700 [thread overview]
Message-ID: <20010829131720.A20537@greenhydrant.com> (raw)
(Sent to linux-raid, linux-kernel and ext3-users since I'm not sure what type of issue
this is)
I've got a test system here running Redhat 7.1 + stock 2.4.9 with these
patches:
http://www.fys.uio.no/~trondmy/src/2.4.9/linux-2.4.9-NFS_ALL.dif
http://www.zip.com.au/~akpm/ext3-2.4-0.9.6-249.gz
http://domsch.com/linux/aacraid/linux-2.4.9-aacraid-20010816.patch
All three patches applied without any problems.
I've got a RAID1 device running over two IDE drives on a Promise controller.
ext3 is the filesystem on the partition. In this machine, the aacraid
driver isn't enabled.
The machine is to be used as a development database server running Sybase
11.9.2. Shortly after installing Sybase and loading some data, I noticed
this:
[sybase@zorro ~]$ uptime
1:01pm up 1 day, 18:29, 3 users, load average: 3.00, 3.00, 2.91
[sybase@zorro ~]$ ps aux | head -15
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1368 72 ? S Aug27 0:05 init [3]
root 2 0.0 0.0 0 0 ? SW Aug27 0:00 [keventd]
root 3 0.0 0.0 0 0 ? SWN Aug27 0:00 [ksoftirqd_CPU0]
root 4 0.0 0.0 0 0 ? SW Aug27 0:03 [kswapd]
root 5 0.0 0.0 0 0 ? SW Aug27 0:00 [kreclaimd]
root 6 0.0 0.0 0 0 ? DW Aug27 0:00 [bdflush]
root 7 0.0 0.0 0 0 ? DW Aug27 0:00 [kupdated]
root 9 0.0 0.0 0 0 ? SW< Aug27 0:00 [mdrecoveryd]
root 10 0.0 0.0 0 0 ? SW< Aug27 0:00 [raid1d]
root 11 0.0 0.0 0 0 ? SW Aug27 0:02 [kjournald]
root 130 0.0 0.0 0 0 ? SW Aug27 0:00 [kjournald]
root 131 0.0 0.0 0 0 ? DW Aug27 0:01 [kjournald]
root 374 0.0 0.0 1428 176 ? S Aug27 0:00 syslogd -m 0
root 379 0.0 0.0 1984 396 ? S Aug27 0:00 klogd -2
[sybase@zorro ~]$
As you can see, bdflush, kupdated and kjournald appear to be deadlocked.
How can I debug this problem and find out who's the problem? I will try
rebooting and to see if the problem returns. If it does, it's back to ext2
for me on this partition, I guess. It seems like it could be a ext3
issue to me...
If there's any more information I can get, let me know. I'll leave the
machine like this for a while before I reboot it.
Thanks,
-Dave
next reply other threads:[~2001-08-29 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 20:17 David Rees [this message]
2001-08-29 20:47 ` kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?) 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
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=20010829131720.A20537@greenhydrant.com \
--to=dbr@greenhydrant.com \
--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.