From: Mike Snitzer <snitzer@redhat.com>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: "Alan D. Brunelle" <Alan.Brunelle@hp.com>,
linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
agk@redhat.com
Subject: Re: Regression in 2.6.31-rc3 (and presumably 2.6.31-rc4?)
Date: Fri, 24 Jul 2009 17:17:56 -0400 [thread overview]
Message-ID: <20090724211756.GA21441@redhat.com> (raw)
In-Reply-To: <8899.1248467518@alphaville.usa.hp.com>
On Fri, Jul 24 2009 at 4:31pm -0400,
Nick Dokos <nicholas.dokos@hp.com> wrote:
> Alan D. Brunelle <Alan.Brunelle@hp.com> wrote:
>
> > I did a diffstat between 2.6.31-rc3 and -rc4 and didn't see anything in
> > the MD space, so...
> >
> > I am unable to create multi-disk LVM striped-volumes with this commit in
> > place - Nick Dokos @ HP did the bisecting and found that removing this
> > commit fixes the same problem for him:
> >
> > 754c5fc7ebb417b23601a6222a6005cc2e7f2913 is first bad commit
> > commit 754c5fc7ebb417b23601a6222a6005cc2e7f2913
> > Author: Mike Snitzer <snitzer@redhat.com>
> > Date: Mon Jun 22 10:12:34 2009 +0100
> >
> > dm: calculate queue limits during resume not load
> >
>
> I pulled from agk's tree after seeing his pull request and applied
> commit 5dea271b6d87bd1d79a59c1d5baac2596a841c37 (plus two more) on
> top of 2.6.41-rc4: I don't see the problem any longer.
Yes, this issue was fixed by that commit (5dea271b6d8). The fix was
first posted to dm-devel 3 weeks ago:
https://www.redhat.com/archives/dm-devel/2009-July/msg00008.html
Regards,
Mike
prev parent reply other threads:[~2009-07-24 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 20:24 Regression in 2.6.31-rc3 (and presumably 2.6.31-rc4?) Alan D. Brunelle
2009-07-24 20:31 ` Nick Dokos
2009-07-24 21:17 ` Mike Snitzer [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=20090724211756.GA21441@redhat.com \
--to=snitzer@redhat.com \
--cc=Alan.Brunelle@hp.com \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nicholas.dokos@hp.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 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.