From: Tejun Heo <tj@kernel.org>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: 2.6.27-rc5-mmotm0829 - lvm issues at boot, possible disk_devt() related?
Date: Mon, 01 Sep 2008 09:58:40 +0200 [thread overview]
Message-ID: <48BBA0B0.5070309@kernel.org> (raw)
In-Reply-To: <4963.1220240176@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> I bisected this down to the 08/28 version of linux-next.patch that was in
> mmotm-0829. 27-rc3-mmotm0814 works fine.
>
> System boots, loads the initrd, starts running. The initrd tries to run lvm
> to find my root file system (the one drive has sda1 a small /boot, and sda2
> is the rest of the disk, and LVM space). Every single partition complains:
>
> device-mapper: core: bdget failed in dm_suspend
> device-mapper: resume ioctl failed: invalid argument
> Unable to resume Volgroup00-root (254:0)
>
> and repeats the 3 lines with different Volgroup-foo and 254:N values for
> each LVM logical volume. After this, it rolls over and dies because it
> didn't find the root filesystem.
>
> This is with an initrd build with Fedora Rawhide current as of last night.
> Using an older initrd that's been working just fine for several releases
> just silently hangs around the lvm startup. (My initrd config does not include
> any .ko files, just nash and lvm and similar early-userspace stuff).
>
> Any ideas? Am willing to try patches/debugging code, if anybody can think
> what I should be instrumenting to get more info.
>
> My gut feeling is an issue in Tejun Heo's patches to implement extended dev
> numbers - one of these two or a related patch:
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.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-09-01 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 3:36 2.6.27-rc5-mmotm0829 - lvm issues at boot, possible disk_devt() related? Valdis.Kletnieks
2008-09-01 3:36 ` Valdis.Kletnieks
2008-09-01 7:58 ` Tejun Heo [this message]
2008-09-01 9:15 ` Valdis.Kletnieks
2008-09-01 9:50 ` Jens Axboe
2008-09-01 9:56 ` Alasdair G Kergon
2008-09-01 9:56 ` [dm-devel] " Alasdair G Kergon
2008-09-01 9:56 ` Alasdair G Kergon
2008-09-01 10:15 ` Jens Axboe
2008-09-01 10:15 ` [dm-devel] " Jens Axboe
2008-09-01 10:15 ` Jens Axboe
2008-09-02 12:16 ` Alan D. Brunelle
2008-09-02 12:16 ` [dm-devel] " 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=48BBA0B0.5070309@kernel.org \
--to=tj@kernel.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.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 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.