From: Jens Axboe <jens.axboe@oracle.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: Tejun Heo <tj@kernel.org>,
device-mapper development <dm-devel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
lvm-devel@redhat.com
Subject: Re: [dm-devel] Re: 2.6.27-rc5-mmotm0829 - lvm issues at boot, possible disk_devt() related?
Date: Mon, 1 Sep 2008 12:15:43 +0200 [thread overview]
Message-ID: <20080901101543.GL20055@kernel.dk> (raw)
In-Reply-To: <20080901095651.GI15123@agk.fab.redhat.com>
On Mon, Sep 01 2008, Alasdair G Kergon wrote:
> On Mon, Sep 01, 2008 at 05:15:58AM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Mon, 01 Sep 2008 09:58:40 +0200, Tejun Heo said:
> > > Yeah, I made a mistake converting two of them and devt lookup fails when
> > > the disk is zero sized. Bartlomiej debugged the problem and posted a
> > > patch and I followed up with an updated patch. It should be fine in the
> > > next round.
> > > http://article.gmane.org/gmane.linux.kernel.next/2663
> > > http://article.gmane.org/gmane.linux.kernel.next/2676
> > > If you're seeing other problems, please let me know.
> > Confirming - 2.6.27-rc5-mmotm0829 plus the merge of the 2 above patches
> > does find the LVM volumes and come up. Thanks for the clue.. :)
>
> I expect we'll need some patches to userspace lvm2 to support these extended
> device numbers properly too...
>
> Alasdair (back from holiday)
They'll be defaulting to off from now on, so it should not be a big
worry. But Alan Brunelle did find that the "10-character limit
in dm/lib/libdm-deptree is too small".
--
Jens Axboe
next prev parent reply other threads:[~2008-09-01 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 3:36 Valdis.Kletnieks
2008-09-01 7:58 ` Tejun Heo
2008-09-01 9:15 ` Valdis.Kletnieks
2008-09-01 9:50 ` Jens Axboe
2008-09-01 9:56 ` [dm-devel] " Alasdair G Kergon
2008-09-01 10:15 ` Jens Axboe [this message]
2008-09-02 12:16 ` Alan D. Brunelle
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=20080901101543.GL20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@redhat.com \
--cc=tj@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
Powered by JetHome