From: "Mike Snitzer" <snitzer@gmail.com>
To: linux-raid@vger.kernel.org
Subject: raid1 with nbd member hangs MD on SLES10 and RHEL5
Date: Tue, 12 Jun 2007 22:30:27 -0400 [thread overview]
Message-ID: <170fa0d20706121930g3b89ddeex8b31c8923d2a0ff6@mail.gmail.com> (raw)
When using raid1 with one local member and one nbd member (marked as
write-mostly) MD hangs when trying to format /dev/md0 with ext3. Both
'cat /proc/mdstat' and 'mdadm --detail /dev/md0' hang infinitely.
I've not tried to reproduce on 2.6.18 or 2.6.19ish kernel.org kernels
yet but this issue affects both SLES10 and RHEL5.
sysrq traces for RHEL5 follow; I don't have immediate access to a
SLES10 system at the moment but I've seen this same hang with SLES10
SP1 RC4:
cat /proc/mdstat
cat S ffff8100048e7de8 6208 11428 11391 (NOTLB)
ffff8100048e7de8 00000000076eb000 ffffffff80098ea6 0000000000000008
ffff81001ff170c0 ffff810037e17100 00045f8d13924085 000000000006b89f
ffff81001ff17290 0000000000000001 0000000000000005 00000000ffffffff
Call Trace:
[<ffffffff80098ea6>] seq_printf+0x67/0x8f
[<ffffffff80233df5>] __mutex_lock_interruptible_slowpath+0x7f/0xbc
[<ffffffff801be644>] md_seq_show+0x123/0x6aa
[<ffffffff8009939f>] seq_read+0x1b8/0x28d
[<ffffffff8007b7a8>] vfs_read+0xcb/0x171
[<ffffffff8007bb87>] sys_read+0x45/0x6e
[<ffffffff800097e1>] tracesys+0xd1/0xdc
/sbin/mdadm --detail /dev/md0
mdadm S ffff810035a1dd78 6384 3829 3828 (NOTLB)
ffff810035a1dd78 ffff81003f4570c0 ffffffff80094e4d 0000000000000001
ffff81000617c870 ffff810037e17100 00043e667c800afe 000000000005ae94
ffff81000617ca40 0000000000000001 0000000000000021 00000000ffffffff
Call Trace:
[<ffffffff80094e4d>] mntput_no_expire+0x19/0x89
[<ffffffff80233df5>] __mutex_lock_interruptible_slowpath+0x7f/0xbc
[<ffffffff801be4e7>] md_open+0x2e/0x68
[<ffffffff80082560>] do_open+0x216/0x316
[<ffffffff8008280b>] blkdev_open+0x0/0x4f
[<ffffffff8008282e>] blkdev_open+0x23/0x4f
[<ffffffff80079889>] __dentry_open+0xd9/0x1dc
[<ffffffff80079a40>] do_filp_open+0x2d/0x3d
[<ffffffff80079a94>] do_sys_open+0x44/0xbe
[<ffffffff800097e1>] tracesys+0xd1/0xdc
I can provided more detailed information; please just ask.
thanks,
Mike
next reply other threads:[~2007-06-13 2:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 2:30 Mike Snitzer [this message]
2007-06-13 2:42 ` raid1 with nbd member hangs MD on SLES10 and RHEL5 Neil Brown
2007-06-13 2:59 ` Mike Snitzer
[not found] ` <170fa0d20706122009h5e3db54ek7487be4940a3d780@mail.gmail.com>
[not found] ` <18031.25581.353761.802283@notabene.brown>
[not found] ` <170fa0d20706122130q2c77d365tbe9261bab1a5b1b@mail.gmail.com>
2007-06-13 18:23 ` Mike Snitzer
2007-06-13 23:30 ` Mike Snitzer
2007-06-14 21:05 ` Bill Davidsen
2007-06-14 21:57 ` Mike Snitzer
2007-06-15 0:40 ` Paul Clements
2007-06-15 1:01 ` Mike Snitzer
2007-06-15 1:05 ` Paul Clements
2007-06-15 1:10 ` Mike Snitzer
2007-06-15 1:16 ` Paul Clements
2007-06-15 1:21 ` Mike Snitzer
2007-06-15 13:21 ` Bill Davidsen
2007-06-15 1:00 ` Paul Clements
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=170fa0d20706121930g3b89ddeex8b31c8923d2a0ff6@mail.gmail.com \
--to=snitzer@gmail.com \
--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 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).