From: Jens Axboe <jens.axboe@oracle.com>
To: Torsten Kaiser <kernel@bardioc.dyndns.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.20-rc3-mm1] raid1 mount blocks for ever
Date: Tue, 9 Jan 2007 13:15:03 +0100 [thread overview]
Message-ID: <20070109121501.GJ11203@kernel.dk> (raw)
In-Reply-To: <20070109120331.GA6108@mail.ustc.edu.cn>
On Tue, Jan 09 2007, Fengguang Wu wrote:
> On Tue, Jan 09, 2007 at 10:19:00AM +0100, Jens Axboe wrote:
> > On Mon, Jan 08 2007, Torsten Kaiser wrote:
> > > On Monday 08 January 2007 09:52, Jens Axboe wrote:
> > > > --- a/block/ll_rw_blk.c
> > > > +++ b/block/ll_rw_blk.c
> > > > @@ -1542,7 +1542,7 @@ static inline void
> > > > - blk_unplug_current();
> > > > + blk_replug_current_nested();
> > >
> > > Does not help. Dmesg follows:
> >
> > [snip]
> >
> > Strange, it works perfectly for me now. Not using -mm though, but the
> > plug branch. And it did hang before. Fengguang, any change for you?
>
> 2.6.20-rc3-mm1 plus your patch works for me.
>
> Lucky enough to found this before giving up:
>
> mount takes 39s, and umount takes 42s.
Do the finish quicker, if you cat /proc/mdstat after issuing the mount
or umount? I'm testing md right now and I'm seeing a few oddities wrt
that, looking further...
You probably also want this, at least if you ever shut down your arrays.
diff --git a/block/ll_rw_blk.c b/block/ll_rw_blk.c
index 4c8ac7e..34b7936 100644
--- a/block/ll_rw_blk.c
+++ b/block/ll_rw_blk.c
@@ -1745,6 +1745,11 @@ request_queue_t *blk_alloc_queue_node(gf
memset(q, 0, sizeof(*q));
+ if (init_qrcu_struct(&q->qrcu)) {
+ kmem_cache_free(requestq_cachep, q);
+ return NULL;
+ }
+
snprintf(q->kobj.name, KOBJ_NAME_LEN, "%s", "queue");
q->kobj.ktype = &queue_ktype;
kobject_init(&q->kobj);
@@ -1802,11 +1807,6 @@ blk_init_queue_node(request_fn_proc *rfn
if (!q)
return NULL;
- if (init_qrcu_struct(&q->qrcu)) {
- kmem_cache_free(requestq_cachep, q);
- return NULL;
- }
-
q->node = node_id;
if (blk_init_free_list(q)) {
cleanup_qrcu_struct(&q->qrcu);
--
Jens Axboe
prev parent reply other threads:[~2007-01-09 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070106025002.GA8330@mail.ustc.edu.cn>
2007-01-06 2:50 ` [BUG 2.6.20-rc3-mm1] raid1 mount blocks for ever Fengguang Wu
2007-01-06 3:59 ` Andrew Morton
[not found] ` <20070106060857.GA6146@mail.ustc.edu.cn>
2007-01-06 6:08 ` Fengguang Wu
2007-01-06 9:51 ` Torsten Kaiser
2007-01-06 10:02 ` Jens Axboe
2007-01-06 10:30 ` Torsten Kaiser
2007-01-06 11:27 ` Jens Axboe
2007-01-08 8:52 ` Jens Axboe
2007-01-08 18:11 ` Torsten Kaiser
2007-01-09 9:19 ` Jens Axboe
[not found] ` <20070109120331.GA6108@mail.ustc.edu.cn>
2007-01-09 12:05 ` Fengguang Wu
2007-01-09 12:15 ` Jens Axboe [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=20070109121501.GJ11203@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=kernel@bardioc.dyndns.org \
--cc=linux-kernel@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