From: Mike Snitzer <snitzer@redhat.com>
To: "Christian Bornträger" <borntraeger@de.ibm.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: regression post 2.6.30: device mapper fails on some logical volumes
Date: Thu, 16 Jul 2009 16:20:29 -0400 [thread overview]
Message-ID: <20090716202028.GA9005@redhat.com> (raw)
In-Reply-To: <200907161746.06935.borntraeger@de.ibm.com>
On Thu, Jul 16 2009 at 11:46am -0400,
Christian Bornträger <borntraeger@de.ibm.com> wrote:
> Am Donnerstag 16 Juli 2009 16:44:39 schrieb Mike Snitzer:
>
> I had another reproduce, and with the latest code (2.6.31-rc3) the mislignment
> warnings from rc1 are indeed gone:
Ah OK, so you were using < 2.6.31-rc2 when you saw all those warnings.
> I now only have
>
> [ 6.283482] device-mapper: table: 253:51: dasdf1 too small for target
> [ 6.283488] device-mapper: table: 253:51: dasde1 too small for target
> [ 6.648895] device-mapper: table: 253:64: dasdc1 too small for target
> [ 6.648900] device-mapper: table: 253:64: dasdd1 too small for target
>
> The logical volumes space-test and space-home still dont appear.
I'm fairly certain that this pending fix will resolve your issues:
http://patchwork.kernel.org/patch/33534/
I'm not sure when Alasdair intends to push it to Linus but it should be
soon.
Mike
next prev parent reply other threads:[~2009-07-16 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 16:52 regression post 2.6.30: device mapper fails on some logical volumes Christian Bornträger
2009-07-15 21:40 ` Mike Snitzer
2009-07-16 5:36 ` Christian Bornträger
2009-07-16 14:44 ` Mike Snitzer
2009-07-16 15:14 ` Christian Bornträger
2009-07-16 15:46 ` Christian Bornträger
2009-07-16 20:20 ` Mike Snitzer [this message]
2009-07-16 21:14 ` Christian Bornträger
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=20090716202028.GA9005@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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