From: NeilBrown <neilb@suse.de>
To: Ray Morris <support@bettercgi.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: debugging md2_resync hang at raise_barrier
Date: Tue, 13 Mar 2012 11:16:33 +1100 [thread overview]
Message-ID: <20120313111633.538c2cd2@notabene.brown> (raw)
In-Reply-To: <20120312134603.703352b8@bettercgi.com>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On Mon, 12 Mar 2012 13:46:03 -0500 Ray Morris <support@bettercgi.com> wrote:
> > On Wed, 29 Feb 2012 18:44:13 -0600 Ray Morris <support@bettercgi.com>
> > wrote:
> >
> > > I am attempting to debug a hang in raid1 and possibly one raid5.
>
>
> On Thu, 1 Mar 2012 12:34:18 +1100
> NeilBrown <neilb@suse.de> wrote:
>
> > I might know what is happening.
> >
> > It is kind-a complicated and involved the magic code in
> > block/blk-core.c:generic_make_request which turns recursive calls
> > into tail recursion.
> ...
> > This patch might fix it. Maybe. If it compiles.
>
> That appears to have solved it. Thanks so much. The delay in my
> response is because I wanted to give it some time to recur, as it
> didn't always manifest right away. Is there anything I should do
> regarding this path in future versions? Is this patch already in or
> planned to be in future versions, or should users possibly keep the
> patch on hand in case it's still needed later? Is there any testing
> or anything that I need to do to get included in future versions?
>
>
Thanks a lot.
I will probably submit this fix to Linus shortly after 3.3 is out, with a
request for it to be included in other -stable releases.
You seem to be using kernels from Redhat. If you want them to include the
patch you should probably raise it as an issue with them.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-03-13 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 0:44 debugging md2_resync hang at raise_barrier Ray Morris
2012-03-01 1:34 ` NeilBrown
2012-03-12 18:46 ` Ray Morris
2012-03-13 0:16 ` NeilBrown [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=20120313111633.538c2cd2@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=support@bettercgi.com \
/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).