From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Guntsche <mike@it-loops.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <jaxboe@fusionio.com>
Subject: Re: 2.6.39 Block layer regression was [Bug] Boot hangs with 2.6.39-rc[123]]
Date: Fri, 15 Apr 2011 00:22:55 -0400 [thread overview]
Message-ID: <20110415042255.GC27928@infradead.org> (raw)
In-Reply-To: <BANLkTi=50A4f_d0a0oESd3DMMaK1za5BWg@mail.gmail.com>
On Thu, Apr 14, 2011 at 08:25:33PM -0700, Linus Torvalds wrote:
> What's the thinking there? It looks very confused to me.
It is. I sent a patch a couple of days ago to fix it.
> Now, clearly RAID seems to be involved in the problem? The main thing
> with that would be that the execution of the requests would tend to
> generate new requests, that go back on the plug queue. Yes? And the
> loop in flush_plug_list() means that they all should get flushed out,
> I assume. But something clearly isn't working, and it does seem to be
> about the RAID kind of setup. So either they didn't get put on the
> plug queue, or the task got a new plug (which _wasn't_ flushed).
>
> Because we're clearly waiting for some request that hasn't completed.
> Where in the plug queues would it be hiding?
There's a thread where Neil explains what the problem with MD is - it
needs a callback on unplug time to generate e.g. the write intent bitmap
or as large as possible writes for RAID5. Jens and Neil have been
looking into it.
next prev parent reply other threads:[~2011-04-15 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 2:06 2.6.39 Block layer regression was [Bug] Boot hangs with 2.6.39-rc[123]] Michael Guntsche
2011-04-15 3:25 ` Linus Torvalds
2011-04-15 4:22 ` Christoph Hellwig [this message]
2011-04-15 6:13 ` Jens Axboe
2011-04-21 17:53 ` Christian Kujau
2011-04-21 17:59 ` Linus Torvalds
2011-04-21 18:30 ` Christian Kujau
2011-04-21 18:36 ` Jens Axboe
2011-04-21 20:53 ` Christian Kujau
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=20110415042255.GC27928@infradead.org \
--to=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@it-loops.com \
--cc=torvalds@linux-foundation.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