From: Andrew Morton <akpm@zip.com.au>
To: David Rees <dbr@greenhydrant.com>
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 15:48:12 -0700 [thread overview]
Message-ID: <3B8D712C.1441BC5A@zip.com.au> (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>, <3B8D60CF.A1400171@zip.com.au>; <20010829144016.C20968@greenhydrant.com> <3B8D6BF9.BFFC4505@zip.com.au>, <3B8D6BF9.BFFC4505@zip.com.au>; from akpm@zip.com.au on Wed, Aug 29, 2001 at 03:26:01PM -0700 <20010829153818.B21590@greenhydrant.com>
David Rees wrote:
>
> ...
>
> The machine was and is still working mostly ok. Since I typed "umount /opt",
> the opt directory doesn't show any contents any more, but before that things
> appear OK. I can still use fdisk to look at the partition layout of the
> drives in /opt raid1 array. /proc/mdstat is normal.
>
> There are no other software raid devices on the machine (/ is also ext3 on a
> separate drive/controller). There are no suspicious messages printed from
> dmesg, either.
>
Are you able to access all the underlying devices on the array?
For example, if /dev/md0 consists of /dev/hda1 and /dev/hdb2,
can you run 'cp /dev/hda1 /dev/null' and 'cp /dev/hdb1 /dev/null'?
If so, then I'm all out of ideas. Your raid1 buffers have disappeared
into thin air :(
-
next prev parent reply other threads:[~2001-08-29 22:48 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 [this message]
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=3B8D712C.1441BC5A@zip.com.au \
--to=akpm@zip.com.au \
--cc=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.